Closed Bug 1159414 Opened 9 years ago Closed 9 years ago

Specifying custom mozharness fails on try

Categories

(Release Engineering :: Applications: MozharnessCore, defect)

Product:
Release Engineering
Component:
Applications: MozharnessCore
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: chmanchester, Unassigned)

Details

I noticed this in https://treeherder.mozilla.org/#/jobs?repo=try&revision=c0d0f611f91a and assumed it was my fault, but also see it in Andrew's push here: https://treeherder.mozilla.org/#/jobs?repo=try&revision=43fd7572822a

The traceback in both is:

12:03:00     INFO -  INFO: copying /builds/adjust-sdk.token to /builds/mock_mozilla/mozilla-centos6-x86_64/root/builds/adjust-sdk.token
12:03:00     INFO -  ERROR: [Errno 2] No such file or directory: '/builds/adjust-sdk.token'
12:03:00     INFO -  Traceback (most recent call last):
12:03:00     INFO -    File "/usr/sbin/mock_mozilla", line 862, in <module>
12:03:00     INFO -      main(retParams)
12:03:00     INFO -    File "/usr/sbin/mock_mozilla", line 823, in main
12:03:00     INFO -      shutil.copy(src, dest)
12:03:00     INFO -    File "/usr/lib64/python2.6/shutil.py", line 84, in copy
12:03:00     INFO -      copyfile(src, dst)
12:03:00     INFO -    File "/usr/lib64/python2.6/shutil.py", line 50, in copyfile
12:03:00     INFO -      with open(src, 'rb') as fsrc:
12:03:00     INFO -  IOError: [Errno 2] No such file or directory: '/builds/adjust-sdk.token'
Oh, I think the pinned rev fell behind default.
Both of our pushes were based off of default, we just got a too recent rev. Basing off the currently pinned revision fixes it.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.