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 could probably HTTP HEAD the build.log and check Content-Length to guess a root.log failure, but it feels weird...

On Fri, Apr 26, 2019 at 6:45 PM Pavel Raiskup <praiskup(a)redhat.com&gt; 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".