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

[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 root.log contains no error or even the status code 110. It turns
out if you look in build.log, the build was actually running and
failed (due to some silly errors on my part). In mock_output.log,
there is some output about mock state inconsistency:

>  ERROR:
> Exception(/var/tmp/koji/tasks/319/37850319/local/work/tasks/300/37850300/golang-tinygo-x-llvm-0-0.6.20190925git95bc4ff.fc32.src.rpm)
> Config(f32-build-17588120-1269812) 0 minutes 25 seconds
>  INFO: Results and/or logs in: /var/lib/mock/f32-build-17588120-1269812/result
>  ERROR: state finish mismatch: current: rpmbuild
> golang-tinygo-x-llvm-0-0.6.20190925git95bc4ff.fc32.src.rpm, state: build phase for
> golang-tinygo-x-llvm-0-0.6.20190925git95bc4ff.fc32.src.rpm 
Somehow mock is getting confused about what state it's in and koji is
stating the wrong place to look.

https://koji.fedoraproject.org/koji/buildinfo?buildID=1389221
https://koji.fedoraproject.org/koji/buildinfo?buildID=1389222
https://koji.fedoraproject.org/koji/buildinfo?buildID=1389223
https://koji.fedoraproject.org/koji/buildinfo?buildID=1389225
https://koji.fedoraproject.org/koji/buildinfo?buildID=1389518

-- 
Elliott

[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

exit code 10 according to:
https://github.com/rpm-software-management/mock/wiki#exit-codes
means "error during rpmbuild"
and indeed there it is:

+ go-rpm-integration check -i tinygo.org/x/go-llvm -b 
/builddir/build/BUILD/go-llvm-95bc4ffe1adda2d3fa986628373a27a674940978/_build/bin -s 
/builddir/build/BUILD/go-llvm-95bc4ffe1adda2d3fa986628373a27a674940978/_build -V
0-0.6.20190925git95bc4ff.fc32 -C 
95bc4ffe1adda2d3fa986628373a27a674940978 -p 
/builddir/build/BUILDROOT/golang-tinygo-x-llvm-0-0.6.20190925git95bc4ff.fc32.arm -g
/usr/share/gocode -r '.*example.*'
Testing    in:
/builddir/build/BUILD/go-llvm-95bc4ffe1adda2d3fa986628373a27a674940978/_build/src
          PATH: 
/builddir/build/BUILD/go-llvm-95bc4ffe1adda2d3fa986628373a27a674940978/_build/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/sbin
        GOPATH:
/builddir/build/BUILD/go-llvm-95bc4ffe1adda2d3fa986628373a27a674940978/_build:/usr/share/gocode
   GO111MODULE: off
       command: go test -buildmode pie -compiler gc -ldflags "-X
tinygo.org/x/go-llvm/version=0 -X 
tinygo.org/x/go-llvm/version.commit=95bc4ffe1adda2d3fa986628373a27a674940978 -extldflags
'-Wl,-z,relro -Wl,--as-needed 
-Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld '"
       testing: tinygo.org/x/go-llvm
tinygo.org/x/go-llvm
# tinygo.org/x/go-llvm
In file included from ./dibuilder.go:17:
./IRBindings.h:47:6: error: conflicting types for 'LLVMSetCurrentDebugLocation2'
    47 | void LLVMSetCurrentDebugLocation2(LLVMBuilderRef Bref, unsigned Line,
       |      ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from ./IRBindings.h:17,
                  from ./dibuilder.go:17:
/usr/include/llvm-c/Core.h:3528:6: note: previous declaration of
'LLVMSetCurrentDebugLocation2' was here
  3528 | void LLVMSetCurrentDebugLocation2(LLVMBuilderRef Builder, LLVMMetadataRef Loc);
       |      ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from ./dibuilder.go:17:
./IRBindings.h:51:29: error: conflicting types for 'LLVMGetCurrentDebugLocation2'
    51 | struct LLVMDebugLocMetadata LLVMGetCurrentDebugLocation2(LLVMBuilderRef Bref);
       |                             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from ./IRBindings.h:17,
                  from ./dibuilder.go:17:
/usr/include/llvm-c/Core.h:3519:17: note: previous declaration of
'LLVMGetCurrentDebugLocation2' was here
  3519 | LLVMMetadataRef LLVMGetCurrentDebugLocation2(LLVMBuilderRef Builder);
       |                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
FAIL	tinygo.org/x/go-llvm [build failed]
error: Bad exit status from /var/tmp/rpm-tmp.VJGsLG (%check)
     Bad exit status from /var/tmp/rpm-tmp.VJGsLG (%check)



-- 
Miroslav Suchy, RHCA
Red Hat, Associate Manager ABRT/Copr, #brno, #fedora-buildsys

[Elliott Sales de Andrade]

On Wed, 25 Sep 2019 at 11:02, Miroslav Suchý <msuchy(a)redhat.com&gt; 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:
>  https://kojipkgs.fedoraproject.org//work/tasks/317/37850317/build.log
>
>  exit code 10 according to:
>  https://github.com/rpm-software-management/mock/wiki#exit-codes
>  means "error during rpmbuild" 
Yes, I know *why* it fails, this is about *how* it fails. Either koji
or mock are confused about what failed. Koji says to look in root.log;
this is wrong, there were no buildroot initialization errors. Mock
also exits with some kind of inconsistency (see original email.)

>  --
>  Miroslav Suchy, RHCA
>  Red Hat, Associate Manager ABRT/Copr, #brno, #fedora-buildsys 
-- 
Elliott

[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ý
> <msuchy(a)redhat.com&gt;
>  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:
>  > https://kojipkgs.fedoraproject.org//work/tasks/317/37850317/build.log
>  > 
>  > exit code 10 according to:
>  > https://github.com/rpm-software-management/mock/wiki#exit-codes
>  > means "error during rpmbuild"
>  
>  Yes, I know *why* it fails, this is about *how* it fails. Either koji
>  or mock are confused about what failed. Koji says to look in
>  root.log;
>  this is wrong, there were no buildroot initialization errors.  
yes , today I noticed this too [2], the error is in build.log and koji
says that in root.log 

>  Mock
>  also exits with some kind of inconsistency (see original email.) 
the error is in build.log

In file included from ./dibuilder.go:17:
./IRBindings.h:47:6: error: conflicting types for
'LLVMSetCurrentDebugLocation2'


[2]
https://koji.fedoraproject.org/koji/taskinfo?taskID=37858379
say error in root.log when the error is in build.log 

>  
>  > --
>  > Miroslav Suchy, RHCA
>  > Red Hat, Associate Manager ABRT/Copr, #brno, #fedora-buildsys
>  
>  -- 
>  Elliott
>  _______________________________________________
>  devel mailing list -- devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  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/[e-mail] 
-- 
Sérgio M. B.

[Miro Hrončok]

On 25. 09. 19 22:01, Elliott Sales de Andrade wrote:
>  On Wed, 25 Sep 2019 at 11:02, Miroslav Suchý
> <msuchy(a)redhat.com&gt; 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:
> > https://kojipkgs.fedoraproject.org//work/tasks/317/37850317/build.log
> >
> > exit code 10 according to:
> > https://github.com/rpm-software-management/mock/wiki#exit-codes
> > means "error during rpmbuild"
>  
>  Yes, I know *why* it fails, this is about *how* it fails. Either koji
>  or mock are confused about what failed. Koji says to look in root.log;
>  this is wrong, there were no buildroot initialization errors. Mock
>  also exits with some kind of inconsistency (see original email.) 
I've opened https://pagure.io/koji/issue/1679

-- 
Miro Hrončok
--
Phone: [phone]
IRC: mhroncok