On Thu, 2020-05-21 at 00:26 +0200, Pavel Raiskup wrote: > On Wednesday, May 20, 2020 11:43:10 PM CEST Michel Alexandre Salim wrote: > > Hi, > > > > I often notice that my scratch build right after updating some packages > > (or packaging them for the first time) would fail -- e.g. due to some > > strict GCC checks -- but Koji would direct me to inspect root.log, even > > though there's no error there and the failure is logged in build.log > > > > One recent example: > > https://koji.fedoraproject.org/koji/taskinfo?taskID=44743799 > > > > Known issue, and if not, where do I report it? > > Probably worth reporting. Koji decides based on mock's exit status; so unless > Koji misinterprets the exit status from mock (would be koji issue), this should > be returned against mock. It's koji that broke, I think. It's been this way for several months, but I never bothered reporting it as I just got used to ignoring what Koji said. It should say root.log if the exit code is 30 and build.log if it's 1 - those are the two most common cases, at least - but it seems to always say root.log even if the exit code is 1, now. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
