Re: Koji build failure misattribution - root.log instead of build.log?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 5/20/20 4:26 PM, Adam Williamson wrote:
On Wed, 2020-05-20 at 16:15 -0700, Adam Williamson wrote:
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.

Aha, these look relevant:

https://pagure.io/koji/c/3f64a48
https://pagure.io/koji/c/c7d35e9

I *suspect* we have only the first deployed right now, and the second
is intended to fix the problem we currently have. If we update our prod
koji to the second, we should get "see build.log or root.log" when the
exit code is 1.

The issue where this is being discussed is
https://pagure.io/koji/issue/1679 .


Thanks for finding this, Adam! I'm following up on that issue.

--
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




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux