Closed
Bug 826116
Opened 13 years ago
Closed 12 years ago
Run B2G mozharness tests using Python 2.7
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: jgriffin, Unassigned)
References
Details
(Whiteboard: [mozharness])
We need to run B2G mozharness tests on Python 2.7 so that our tweaks to unittest work consistently (ala bug 803254). I believe that Python 2.7 is already installed on the slaves, so this is probably just a matter of updating the relevant mozharness configs to point to the right Python.
We're currently using this:
"exes": {
'python': '/tools/buildbot/bin/python',
'virtualenv': ['/tools/buildbot/bin/python', '/tools/misc-python/virtualenv.py'],
'tooltool.py': "/tools/tooltool.py",
},
Aki, what should those values be for Python 2.7 on the linux 32 slaves? We can test this out on ash (mozharness try) as soon as bug 826026 is closed.
Comment 1•13 years ago
|
||
IIRC, we have python 2.6 or 2.7 on all test slaves.
We're already pointing at the newest.
Bug 724191 tracks installing and using 2.7[.3, I believe] everywhere.
Depends on: 724191
Updated•13 years ago
|
Whiteboard: [mozharness]
Comment 2•12 years ago
|
||
I think we're already doing this.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Comment 3•12 years ago
|
||
I think linux is good. I'm not sure about OSX.
Assignee | ||
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
Assignee | ||
Updated•7 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•