Bug 2382955 - libusb-compat-0.1: STI tests will no longer be run in F43
Summary: libusb-compat-0.1: STI tests will no longer be run in F43
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: libusb-compat-0.1
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kate Hsuan
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: Disable, STI
TreeView+ depends on / blocked
 
Reported: 2025-07-23 13:47 UTC by Cristian Le
Modified: 2025-08-11 08:30 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-08-11 08:30:43 UTC
Type: ---
Embargoed:
hpa: mirror+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FC-1890 0 None None None 2025-08-04 04:22:14 UTC

Description Cristian Le 2025-07-23 13:47:39 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 Kate Hsuan 2025-08-04 03:46:45 UTC
I'll fix it.
Thank you.

Comment 2 Kate Hsuan 2025-08-11 08:30:43 UTC
The test was migrated to tmt test and the commit can be found here.
https://src.fedoraproject.org/rpms/libusb-compat-0.1/c/bec01398435e39d52184e676c8a31eb632edd6bb?branch=rawhide
This issue can be closed.


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