1159414 - Specifying custom mozharness fails on try

Status: RESOLVED WORKSFORME

(Release Engineering :: Applications: MozharnessCore, defect)

Description

[Chris Manchester (limited bugmail, email directly)]

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'

Comment 1

[Legacy TBPL/Treeherder Robot]

log: https://treeherder.mozilla.org/logviewer.html#?repo=try&job_id=7016428
repository: try
start_time: 2015-04-28T12:02:39
who: ahalberstadt[at]mozilla[dot]com
machine: try-linux64-spot-307
buildname: Linux try build
revision: 43fd7572822a

IOError: [Errno 2] No such file or directory: '/builds/adjust-sdk.token'
Return code: 1
1 not in success codes: [0]
Halting on failure while running ['mock_mozilla', '-r', 'mozilla-centos6-x86_64', '--copyin', '--unpriv', '/builds/adjust-sdk.token', '/builds/adjust-sdk.token']
Running post_fatal callback...
Exiting 3
# TBPL EXCEPTION #
# TBPL EXCEPTION #

Comment 2

[Chris Manchester (limited bugmail, email directly)]

Oh, I think the pinned rev fell behind default.

Comment 3

[Chris Manchester (limited bugmail, email directly)]

Both of our pushes were based off of default, we just got a too recent rev. Basing off the currently pinned revision fixes it.