Hey!
Koji is always very nice and it tells me whether a build failure was caused by root.log or build.log. See for example:
https://koji.fedoraproject.org/koji/taskinfo?taskID=28963878 BuildError: error building package (arch x86_64), mock exited with status 1; see build.log for more information
Is Copr presenting this kind of information somewhere? (I need to fetch it for hundreds of builds.)
I could probably HTTP HEAD the build.log and check Content-Length to guess a root.log failure, but it feels weird...
Thanks for tips.
On Friday, April 26, 2019 4:13:30 PM CEST Miro Hrončok wrote:
Koji is always very nice and it tells me whether a build failure was caused by root.log or build.log. See for example:
https://koji.fedoraproject.org/koji/taskinfo?taskID=28963878 BuildError: error building package (arch x86_64), mock exited with status 1; see build.log for more information
Is Copr presenting this kind of information somewhere?
No. If koji really does some log analysis, I'd love to review "backport" pull-request of the same logic. Or at least fill an issue.
I could probably HTTP HEAD the build.log and check Content-Length to guess a root.log failure, but it feels weird...
The log analysis done by Copr won't be much nicer, I suppose... unless there's some mock API copr forgot to use for this purpose.
Pavel
On Fri, Apr 26, 2019 at 6:45 PM Pavel Raiskup praiskup@redhat.com wrote:
On Friday, April 26, 2019 4:13:30 PM CEST Miro Hrončok wrote:
Koji is always very nice and it tells me whether a build failure was caused by root.log or build.log. See for example:
https://koji.fedoraproject.org/koji/taskinfo?taskID=28963878 BuildError: error building package (arch x86_64), mock exited with status 1; see build.log for more information
Is Copr presenting this kind of information somewhere?
No. If koji really does some log analysis, I'd love to review "backport" pull-request of the same logic. Or at least fill an issue.
The logic used by Koji is simple: if mock exits with status code 1 then it's "build.log". Otherwise (terminates with a signal or exits with code other than 1) it is "root.log".
-- Mikolaj Izdebski
On Saturday, April 27, 2019 1:11:49 AM CEST Mikolaj Izdebski wrote:
On Fri, Apr 26, 2019 at 6:45 PM Pavel Raiskup praiskup@redhat.com wrote:
On Friday, April 26, 2019 4:13:30 PM CEST Miro Hrončok wrote:
Koji is always very nice and it tells me whether a build failure was caused by root.log or build.log. See for example:
https://koji.fedoraproject.org/koji/taskinfo?taskID=28963878 BuildError: error building package (arch x86_64), mock exited with status 1; see build.log for more information
Is Copr presenting this kind of information somewhere?
No. If koji really does some log analysis, I'd love to review "backport" pull-request of the same logic. Or at least fill an issue.
The logic used by Koji is simple: if mock exits with status code 1 then it's "build.log". Otherwise (terminates with a signal or exits with code other than 1) it is "root.log".
Thanks, I created this now: https://pagure.io/copr/copr/issue/835
FWIW, here's one attempt to actually parse the mock logs: https://github.com/rebase-helper/rebase-helper/blob/4e9458ae1fc46d37acd8a1a9...
Pavel
copr-devel@lists.fedorahosted.org
-
Mikolaj Izdebski -
Miro Hrončok -
Pavel Raiskup