Bug 2382936 - knot-resolver: STI tests will no longer be run in F43
Summary: knot-resolver: STI tests will no longer be run in F43
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: knot-resolver
Version: 45
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jakub Ružička
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: Disable, STI
TreeView+ depends on / blocked
 
Reported: 2025-07-23 13:46 UTC by Cristian Le
Modified: 2026-10-14 20:48 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2026-10-14 16:00:39 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Cristian Le 2025-07-23 13:46:09 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 Aoife Moloney 2026-08-17 13:53:25 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 45 development cycle.
Changing version to 45.

Comment 2 Cristian Le 2026-10-14 16:56:13 UTC
Noticed that you still have it mentioned in `gating.yaml`, although curiously it was never triggered https://src.fedoraproject.org/rpms/knot-resolver/blob/rawhide/f/gating.yml

Comment 3 Jan Včelák 2026-10-14 20:48:35 UTC
Just removed that. Thanks for noticing.


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