On Fri, May 31, 2019 at 08:34:59AM -0700, Adam Williamson wrote:
The 'test case names' here are the names as they appear in resultsdb.
Both of those exist, though dist.depcheck hasn't actually been used
since July 2017, so we should probably replace that name as an example:
https://taskotron.fedoraproject.org/resultsdb/results?&testcases=dist...
https://taskotron.fedoraproject.org/resultsdb/results?&testcases=org....
I am not 100% sure what resultsdb test name the results of a per-
package test like this would show up under, but as these tests are run
in the CI pipeline it probably actually *is*
org.centos.prod.ci.pipeline.allpackages-
build.package.test.functional.complete , which would be why that
existing package uses it.
Thanks for confirming this, it seems that failed
org.centos.prod.ci.pipeline.allpackages-build.package.test.functional.complete
gates the update correctly:
https://bodhi.fedoraproject.org/updates/FEDORA-2019-e00e77df62
What is the best way to get this added to the general documentation of
Fedora CI and gating? Should I take this to ci@lists?
--
Jan Pazdziora
Sr. Principal Software Engineer, Security Engineering, Red Hat