I've built a package today for rawhide, it got errata
created automatically and
finished for it in half an hour or so.
The I've done the same build for Fedora 32, I've filed
for it but since then
is stuck as missing. The red rectangle is not clickable, so it's hard
to see if the test was actually scheduled, if CI knows about the new
build, what is going on.
Could anyone with insight into the Fedora CI process take a look to
see where things got stuck, and also recommend how to do the check
in the future myself?
Product Owner, Platform Security Readiness, Red Hat
I'm trying to wrap up the work to get rpminspect running on all builds
coming out of koji and I've run into some questions about the messages
I'm emitting and what should be in resultsdb.
Do error messages (koji-build.test.error) belong in resultsdb?
If an error condition is reached, should both a completion
(koji-build.test.complete) and an error message be emitted? I'm unclear
if exiting with an error condition constitutes completion or not.
I'd appreciate input that folks have on this.