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

2020-05-22 Thread Michel Alexandre Salim
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

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

2020-05-20 Thread Adam Williamson
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 > > >

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

2020-05-20 Thread Adam Williamson
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 >

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

2020-05-20 Thread Pavel Raiskup
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

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

2020-05-20 Thread Michel Alexandre Salim
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