I;ve been getting intermittent s390x build failures, for example:
https://koji.fedoraproject.org/koji/taskinfo?taskID=37763977 https://koji.fedoraproject.org/koji/taskinfo?taskID=37763055
The relevant part of the logs is from mock_output.log:
Start: build phase for eclipse-4.13-2.module_f31+6519+12cd0b27.src.rpm Start: build setup for eclipse-4.13-2.module_f31+6519+12cd0b27.src.rpm Finish: build setup for eclipse-4.13-2.module_f31+6519+12cd0b27.src.rpm Finish: build phase for eclipse-4.13-2.module_f31+6519+12cd0b27.src.rpm ERROR: Exception(/var/tmp/koji/tasks/3055/37763055/local/work/tasks/2985/37762985/eclipse-4.13-2.module_f31+6519+12cd0b27.src.rpm) Config(module-eclipse-latest-3120190920120950-d36a98d4-build-17552893-1266828) 0 minutes 0 seconds INFO: Results and/or logs in: /var/lib/mock/module-eclipse-latest-3120190920120950-d36a98d4-build-17552893-1266828/result ERROR: Command failed: # /bin/rpm -Uvh --nodeps /builddir/build/originals/eclipse-4.13-2.module_f31+6519+12cd0b27.src.rpm
Metadata Update from @bowlofeggs: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: koji
We have seen this before in ticket 8029, which we reported upstream to koji folks:
https://pagure.io/koji/issue/1418
Can you add info there and follow along to see if we can track it down.
Metadata Update from @kevin: - Issue close_status updated to: Upstream - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.