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. Pavel > > Thanks, > > -- > Michel Alexandre Salim > profile: https://keybase.io/michel_slm > chat via email: https://delta.chat/ > GPG key: 96A7 A6ED FB4D 2113 4056 3257 CAF9 AD10 ACB1 BEF2 > _______________________________________________ > 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 > _______________________________________________ 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
