Closed Bug 1150205 Opened 11 years ago Closed 11 years ago

Unable to run tests (unit/integration) on OSX Yosemite

Categories

(Testing Graveyard :: JSMarionette, defect)

Product:
Testing Graveyard
Component:
JSMarionette
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: kgrandon, Unassigned)

References

Details

Running the command I see this error: ./scripts/setup_python.sh: /usr/local/bin/virtualenv: /usr/bin/python: bad interpreter: No such file or directory Running `which python` shows me this location: /Library/Frameworks/Python.framework/Versions/2.7/bin/python This was working fine for me prior to the runner bump and reverting this fixes it for me: https://github.com/mozilla-b2g/gaia/commit/88f9ee509717ff2c297fa67db2f4ed9721c94350 This is a *huge* productivity impact for me, so if you guys have any suggestions I would appreciate it. Thanks!
Hey guys - any ideas about this? Any additional information I can provide to help track this down? Is this working for anyone else running 10.10.2?
Flags: needinfo?(jlal)
Flags: needinfo?(jgriffin)
Flags: needinfo?(gaye)
Can you point me to where setup_python.sh lives?
Flags: needinfo?(jgriffin)
@kgrandon Kicking off an upgrade for my mac @jgriffin https://github.com/mozilla-b2g/marionette-js-runner/blob/master/scripts/setup_python.sh
Flags: needinfo?(jlal)
This is probably caused by having virtualenv installed from before your upgrade, and having it point to the wrong place. You may be able to fix it by editing /usr/local/bin/virtualenv to point to the correct location of Python. Alternatley, you may uninstall virtualenv and then re-install it.
(In reply to Jonathan Griffin (:jgriffin) from comment #4) > Alternatley, you may uninstall virtualenv and then re-install it. If you installed it using 'pip install virtualenv', you can: sudo pip uninstall virtualenv then sudo pip install virtualenv
(In reply to Jonathan Griffin (:jgriffin) from comment #5) > (In reply to Jonathan Griffin (:jgriffin) from comment #4) > > Alternatley, you may uninstall virtualenv and then re-install it. > > If you installed it using 'pip install virtualenv', you can: > > sudo pip uninstall virtualenv > then > sudo pip install virtualenv You saved my life! Everything seems to be working properly after the reinstall. Thanks for the pointer.
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(gaye)
Resolution: --- → WORKSFORME
Thanks jgrifffin :)
Product: Testing → Testing Graveyard
You need to log in before you can comment on or make changes to this bug.