Bug 2382969 - mariadb10.11: STI tests will no longer be run in F43
Summary: mariadb10.11: STI tests will no longer be run in F43
Keywords:
Status: CLOSED COMPLETED
Alias: None
Product: Fedora
Classification: Fedora
Component: mariadb10.11
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Pavol Sloboda
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: Disable, STI 2388185
TreeView+ depends on / blocked
 
Reported: 2025-07-23 13:59 UTC by Cristian Le
Modified: 2026-02-04 08:51 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
: 2388185 (view as bug list)
Environment:
Last Closed: 2026-02-04 08:51:23 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Cristian Le 2025-07-23 13:59:25 UTC
Dear package maintainer,

This is an automated bug created due to the announced change proposal Disablement of STI tests.

Your project still has STI tests under `tests/tests*.yml`, which will no longer be run soon. We suggest you
migrate these tests to TMT format instead.

In the simplest case when the STI tests is a simple wrapper around a `tests/run_tests.sh`, the migration would
look like this:
```
$ tmt init
$ rm tests/tests.yml
$ cat <<EOF > ./plans.fmf
summary: Run all smoke tests
discover:
  how: fmf
execute:
  how: tmt
EOF
$ cat <<EOF > ./tests/main.fmf
summary: Smoke test
test: ./run_tests.sh
EOF
```

See https://fedoraproject.org/wiki/Changes/DisableSTI for more information, including a link to a migration
guide.

Feel free to reach out to us here or in #fedora-ci or #tmt matrix rooms if you need any help.

Comment 1 Pavol Sloboda 2025-07-31 10:48:31 UTC
Hello, I have looked into the change and I will be working on a fix

Comment 2 Pavol Sloboda 2026-02-04 08:51:23 UTC
This has been resolved by a rework of the tmt plans in the repository that now run the centos-stream tests for mariadb.
The plans were finalized in this commit: https://src.fedoraproject.org/rpms/mariadb10.11/c/488ff36c8a79397b48ed03e5dbdd7a5841dbe473?branch=rawhide


Note You need to log in before you can comment on or make changes to this bug.