I'm seeing this strange error when I'm trying to build GDB on Koji (s390x builder):
https://koji.fedoraproject.org/koji/taskinfo?taskID=40824847
Traceback (most recent call last): File "/usr/lib/python3.7/site-packages/koji/daemon.py", line 1294, in runTask response = (handler.run(),) File "/usr/lib/python3.7/site-packages/koji/tasks.py", line 313, in run return koji.util.call_with_argcheck(self.handler, self.params, self.opts) File "/usr/lib/python3.7/site-packages/koji/util.py", line 263, in call_with_argcheck return func(*args, **kwargs) File "/usr/sbin/kojid", line 1343, in handler h = koji.get_rpm_header(fn) File "/usr/lib/python3.7/site-packages/koji/__init__.py", line 914, in get_rpm_header hdr = ts.hdrFromFdno(fo.fileno()) File "/usr/lib64/python3.7/site-packages/rpm/transaction.py", line 185, in hdrFromFdno raise rpm.error("error reading package header") _rpm.error: error reading package header
The other architectures are able to finish the build just fine, but s390x fails like above.
This is likely a transitory network issue (as all the s390x builders are remote).
Does it persist? or was this a one time thing?
Metadata Update from @kevin: - Issue priority set to: Waiting on Assignee (was: Needs Review)
I think it's just better diagnostics from new koji, but in fact the same issue we had earlier about "broken srpm downloads". There were changes to improve the diagnostics on the koji side.
This is likely a transitory network issue (as all the s390x builders are remote). Does it persist? or was this a one time thing?
I haven't tried again. I'm doing a new build right now; will let you know when it finished.
The next attempt succeeded, so I'm closing this issue. Thanks.
Metadata Update from @sergiodj: - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.