Re: "mock exited with status 110, see root.log for more information"; but it's a build failure

2019-10-04 Thread Miro Hrončok
On 25. 09. 19 22:01, Elliott Sales de Andrade wrote: On Wed, 25 Sep 2019 at 11:02, Miroslav Suchý wrote: Dne 25. 09. 19 v 4:59 Elliott Sales de Andrade napsal(a): https://koji.fedoraproject.org/koji/buildinfo?buildID=1389518 I looked at this one and:

Re: "mock exited with status 110, see root.log for more information"; but it's a build failure

2019-09-25 Thread Sérgio Basto
On Wed, 2019-09-25 at 16:01 -0400, Elliott Sales de Andrade wrote: > On Wed, 25 Sep 2019 at 11:02, Miroslav Suchý > wrote: > > Dne 25. 09. 19 v 4:59 Elliott Sales de Andrade napsal(a): > > > https://koji.fedoraproject.org/koji/buildinfo?buildID=1389518 > > > > I looked at this one and: > > > >

Re: "mock exited with status 110, see root.log for more information"; but it's a build failure

2019-09-25 Thread Elliott Sales de Andrade
On Wed, 25 Sep 2019 at 11:02, Miroslav Suchý wrote: > > Dne 25. 09. 19 v 4:59 Elliott Sales de Andrade napsal(a): > > https://koji.fedoraproject.org/koji/buildinfo?buildID=1389518 > > I looked at this one and: > > https://koji.fedoraproject.org/koji/taskinfo?taskID=37850317 > and build log: >

Re: "mock exited with status 110, see root.log for more information"; but it's a build failure

2019-09-25 Thread Miroslav Suchý
Dne 25. 09. 19 v 4:59 Elliott Sales de Andrade napsal(a): https://koji.fedoraproject.org/koji/buildinfo?buildID=1389518 I looked at this one and: https://koji.fedoraproject.org/koji/taskinfo?taskID=37850317 and build log: https://kojipkgs.fedoraproject.org//work/tasks/317/37850317/build.log

"mock exited with status 110, see root.log for more information"; but it's a build failure

2019-09-24 Thread Elliott Sales de Andrade
Yesterday, I saw this error periodically in a few random arches, and today I saw it more often (see examples at end of email). The individual builds say something like: > BuildError: error building package (arch x86_64), mock exited with status > 110; see root.log for more information but