fedora-ci / general

#146 CI tests would be useful right after the build
Opened by adelton. Modified

Open
Close Issue

Based on explanation by Bruno in thread https://lists.fedoraproject.org/archives/list/ci@lists.fedoraproject.org/thread/57ZHN2I3K2NW23VEIPAKFBZNTX2FHZCL/, CI tests are only triggered for Fedora 33 builds once the errata is promoted to testing status. When maintainer wants to make sure that the build + errata work is done and they no longer need to worry about it, waiting for nondeterministic period of time for the errata to move to testing for the tests to even start seems wasteful. In general I'd expect the errata to be in that "failed because pending" status for minimum amount of time and tests run as soon as possible.

Unless there is a strong reason to wait until the errata is in testing state, could the CI tests be run right away?

Looking at the documentation:
https://fedoraproject.org/wiki/Bodhi#Pending

Seems we could trigger on Pending, but it could cause some false positives, but I would not be afraid to try it out.

@bgoncalv @pingou is there a reason why we could not trigger on pending state so this problem the user is describing is mitigated and he can get results in a more reasonable time?

Rawhide updates should not go via pending. If they do, that is a bodhi bug. IIRC, there was such a bug in bodhi on multi-builds updates and it got recently fixed.

Rawhide updates work fine, the tests start right away. This is about Fedora 33 updates.
Edited by adelton

I'm fine to try to trigger on pending status.

I just want to confirm if the topic for the trigger would be org.fedoraproject.prod.bodhi.update.request.testing ?

Also does Rawhide updates also sends the same topic? Just to avoid to have to trigger on 2 different topics.
Edited by bgoncalv

@pingou could you answer pls @bgoncalv questions pls?

Documentation is not clear :(

https://fedmsg2.readthedocs.io/en/latest/topics.html#bodhi-update-request-testing

and below is again the same topic:

https://fedmsg2.readthedocs.io/en/latest/topics.html#id32

Hello, I've just hit the same problem with https://bodhi.fedoraproject.org/updates/FEDORA-2021-4adc4e0f3f -- tests are missing, it's not even clear where the Fedora 34 pipeline is.

@mvadkert, could the pipeline configuration be changed to see tests executed in a timely manner?

Metadata Update from @msrb:
- Issue assigned to msrb

checking...

@msrb I do not see a reason why not to run them earlier from my perspective ... do we need more discussion with @bookwar ?

@adelton

@mvadkert, could the pipeline configuration be changed to see tests executed in a timely manner?

This is not a piece I own, but I support your ask

I filed https://github.com/fedora-infra/bodhi/issues/4187 against Bodhi.
Metadata
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.