jobrunner (from taskotron-trigger-0.5.0-1.fc27.noarch) crashed immediately after start.
# sudo -u fedmsg jobrunner --start 1522916918 No handlers could be found for logger "moksha.hub" 2018-04-05 08:34:16 - Jobrunner - INFO: Processing jobs from datagrepper for topic org.fedoraproject.prod.buildsys.build.state.change: page 1 of 1 Traceback (most recent call last): File "/bin/jobrunner", line 11, in <module> load_entry_point('jobtriggers==0.5.0', 'console_scripts', 'jobrunner')() File "/usr/lib/python2.7/site-packages/jobtriggers/jobrunner.py", line 112, in main datagrepper_jobs(args.start, args.end) File "/usr/lib/python2.7/site-packages/jobtriggers/jobrunner.py", line 86, in datagrepper_jobs data = trigger.process(msg) File "/usr/lib/python2.7/site-packages/jobtriggers/koji_build_msg.py", line 83, in process return self._process_package(msg) File "/usr/lib/python2.7/site-packages/jobtriggers/koji_build_msg.py", line 28, in _process_package critpath_pkgs = critpath['pkgs'].get(distgit_branch, critpath['pkgs']['master']) TypeError: 'NoneType' object has no attribute '__getitem__'
Judging from the traceback, this might be likely related to this ticket: https://pagure.io/taskotron/issue/230 In a nutshell, we no longer pull critpath list properly.
Metadata Update from @kparal: - Issue tagged with: bug
@kparal what does "we no longer pull critpath list properly"? Thing is, if the file is not parse-able, then triggering on koji-build messages won't work at all (that file gets parsed for each koji-build fedmsg). If it just does not work from jobrunner then there is some weird issue in there.
jobrunner
Log in to comment on this ticket.