Closed
Bug 1167648
Opened 9 years ago
Closed 9 years ago
Tryserver Windows XP debug Sm failures due to python 2.6 being installed instead of 2.7
Categories
(Infrastructure & Operations :: RelOps: General, task)
Infrastructure & Operations
RelOps: General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: erahm, Assigned: grenade)
Details
It looks like running the Sm tests is failing occasionally on Windows XP try servers due to the wrong python version being installed. Treeherder:https://treeherder.mozilla.org/#/jobs?repo=try&revision=b9110f32cbf8 Log: http://ftp.mozilla.org/pub/mozilla.org/spidermonkey/try-builds/jinank94@gmail.com-b9110f32cbf8/try-win32-debug/try_win32-debug_spidermonkey-plaindebug-bm87-try1-build107.txt.gz Snippet > checking for python2.7... no > checking for python... /c/mozilla-build/python/python > Creating Python environment > Python 2.7.3 or greater (but not Python 3) is required to build. You are running Python 2.6.5. > Please upgrade to the latest MozillaBuild development environment. See https://developer.mozilla.org/en-US/docs/Developer_Guide/Build_Instructions/Windows_Prerequisites
Comment 1•9 years ago
|
||
Digging in a little -- scripts/scripts/spidermonkey_builds/spidermonkey.sh is what is having the issue.
Comment 2•9 years ago
|
||
From that try job: b-2008-ix-0039 b-2008-ix-0028 b-2008-ix-0048 b-2008-ix-0045 b-2008-ix-0033 (https://treeherder.mozilla.org/#/jobs?repo=try&revision=173ac2b27abd)
Comment 3•9 years ago
|
||
:markco had a look and two jobs were running. It appeared to both have buildbot and runner going at the same time as well.
Assignee | ||
Comment 4•9 years ago
|
||
Affected machines were: B-2008-IX-0018 B-2008-IX-0020 B-2008-IX-0021 B-2008-IX-0022 B-2008-IX-0023 B-2008-IX-0024 B-2008-IX-0025 B-2008-IX-0026 B-2008-IX-0027 B-2008-IX-0028 B-2008-IX-0029 B-2008-IX-0030 B-2008-IX-0031 B-2008-IX-0032 B-2008-IX-0033 B-2008-IX-0034 B-2008-IX-0035 B-2008-IX-0036 B-2008-IX-0037 B-2008-IX-0038 B-2008-IX-0039 B-2008-IX-0040 B-2008-IX-0041 B-2008-IX-0042 B-2008-IX-0043 B-2008-IX-0044 B-2008-IX-0045 B-2008-IX-0046 B-2008-IX-0047 B-2008-IX-0048 B-2008-IX-0049 B-2008-IX-0055 B-2008-IX-0056 B-2008-IX-0057 B-2008-IX-0058 B-2008-IX-0059 B-2008-IX-0060 B-2008-IX-0061 B-2008-IX-0062 B-2008-IX-0063 B-2008-IX-0064 B-2008-IX-0173 B-2008-IX-0174 B-2008-IX-0181 B-2008-IX-0182 B-2008-IX-0183 B-2008-IX-0184
Assignee | ||
Comment 5•9 years ago
|
||
So, this happened because I did an incomplete roll-back of the original try runner rollout from last week. I had failed to understand that the builders only require the opt folder if runner is in use and so failed to remove the folder as part of the roll-back. The folder has now been removed. It shouldn't be possible for runner to run on these machines now.
Reporter | ||
Comment 6•9 years ago
|
||
It's not clear to me whether or not this is still an issue. Are we just in the postmortem phase now?
Flags: needinfo?(rthijssen)
Comment 7•9 years ago
|
||
This should no longer be an issue. I was corrected as of 2015-05-22 14:09:18 EDT.
Assignee: relops → rthijssen
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(rthijssen)
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•