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.depcheck&since=2017-01-02T00:00:00,2019-05-31T23:59:59 > https://taskotron.fedoraproject.org/resultsdb/results?&testcases=org.centos.prod.ci.pipeline.allpackages-build.package.test.functional.complete&since=2019-02-01T00:00:00,2019-05-31T23:59:59 > > 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 _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
