See this build for an example:
http://koji.stg.fedoraproject.org/koji/taskinfo?taskID=90084896
We get this:
Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/koji/daemon.py", line 1160, in runTask response = (handler.run(),) File "/usr/lib/python2.7/site-packages/koji/tasks.py", line 158, in run return koji.util.call_with_argcheck(self.handler, self.params, self.opts) File "/usr/lib/python2.7/site-packages/koji/util.py", line 156, in call_with_argcheck return func(*args, **kwargs) File "/usr/sbin/kojid", line 833, in handler srpm = self.getSRPM(src, build_tag, repo_info['id']) File "/usr/sbin/kojid", line 883, in getSRPM return self.getSRPMFromSCM(src, build_tag, repo_id) File "/usr/sbin/kojid", line 899, in getSRPMFromSCM srpm = result['srpm'] KeyError: 'srpm'
This is using koji-builder-1.10.1-10.fc25.1 from https://pagure.io/fork/ausil/koji/branch/fedora-infra
Better info: @ausil says that https://pagure.io/fork/ausil/koji/commits/fedora-infra-201610 is the code that is deployed there (in staging).
that is not that code that is deployed in stg https://pagure.io/fork/ausil/koji/commits/fedora-infra-201610 is which is master plus a few patches we needed to test
Oh, the problem is not the traceback. The problem really comes from the subtask where git reset ... fails: http://koji.stg.fedoraproject.org/koji/taskinfo?taskID=90084897
git reset ...
The failed subtask should have raised an exception in the parent task.
@ausil pointed out that the child task is trying to git reset --hard f25 when it should instead be trying to git reset --hard abcdefdeadbeef.
git reset --hard f25
git reset --hard abcdefdeadbeef
Yeah, the problem is on our side. Not koji's fault. This issue can be closed. Thanks!
@mikeb changed the status to Closed
Closed
This issue has been migrated to Fedora Forge: https://forge.fedoraproject.org/koji/koji/issues/211
Please continue any further discussion there.