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