> On 29 Sep 2017, at 15:58, Monty Taylor <mordred at inaugust.com> wrote: > > tl;dr - If you're having issues with your jobs, check the FAQ, this email and followups on this thread for mentions of them. If it's an issue with your job and you can spot it (bad config) just submit a patch with topic 'zuulv3'. If it's bigger/weirder/you don't know - we'd like to ask that you send a follow up email to this thread so that we can ensure we've got them all and so that others can see it too. Hello, Automated requirements updates [1] are all failing with the same error in the run.yaml playbook of the legacy-requirements job, e.g. in python-blazarclient [2]. The command `/usr/local/jenkins/slave_scripts/project-requirements-change.py $ZUUL_BRANCH` fails with: SystemError: error: pathspec 'remotes/origin/master' did not match any file(s) known to git. or, for patches using the Pike stable branch: SystemError: error: pathspec 'remotes/origin/stable/pike' did not match any file(s) known to git. [1] https://review.openstack.org/#/q/topic:openstack/requirements+status:open <https://review.openstack.org/#/q/topic:openstack/requirements+status:open> [2] http://logs.openstack.org/50/509450/9/check/legacy-requirements/914355a/ara/ <http://logs.openstack.org/50/509450/9/check/legacy-requirements/914355a/ara/> Best regards, Pierre Riteau -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20171005/b24f3483/attachment.html>