Bug 2382951 - libssh: STI tests will no longer be run in F43
Summary: libssh: STI tests will no longer be run in F43
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: libssh
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Andreas Schneider
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: Disable, STI
TreeView+ depends on / blocked
 
Reported: 2025-07-23 13:47 UTC by Cristian Le
Modified: 2025-07-25 13:55 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-07-25 13:35:57 UTC
Type: ---
Embargoed:
fedora-admin-xmlrpc: mirror+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FC-1848 0 None None None 2025-07-23 13:48:34 UTC

Description Cristian Le 2025-07-23 13:47:19 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 Jakub Jelen 2025-07-25 13:35:57 UTC
Removed the tests as they were really empty for quite some time (pointing to empty repo):

https://src.fedoraproject.org/rpms/libssh/c/b4f7ff9ad5fd5002bede061fb7cb14d5d03502ee?branch=rawhide

Comment 2 Cristian Le 2025-07-25 13:50:47 UTC
They seem to have been migrated to a different repo, but they should still be somewhere. Can't deduce where they are now though unfortunately

Comment 3 Jakub Jelen 2025-07-25 13:55:47 UTC
Yes, they were moved to internal repo.


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