|Submitter||Diff||Changes||Open Issues||Last Updated|
|Error loading review requests:|
58 bytes, text/x-review-board-request
|Details | Review|
I realized that the mach environment in the interactive worker wasn't using the proper virtualenv (in /home/worker/workspace/build/venv). This manifested in an ImportError: No module named 'requests'. Even though most of the packages (except requests) are already added to sys.path by the mach bootstrap, it's definitely best if we simply re-use the virtualenv altogether. I found the easiest way to get mach to use the virtualenv is to add /home/worker/workspace/build/venv/bin to the $PATH.
Created attachment 8775713 [details] Bug 1289879 - Activate the mozharness virtualenv when running tests on interactive workers, There are some packages like 'requests' that are bundled in the mozharness venv, but not in the test package. It would be easy to manually add these to sys.path in the mach bootstrap script, but it's much nicer to simply activate this virtualenv in the first place. Review commit: https://reviewboard.mozilla.org/r/67850/diff/#index_header See other reviews: https://reviewboard.mozilla.org/r/67850/
Comment on attachment 8775713 [details] Bug 1289879 - Activate the mozharness virtualenv when running tests on interactive workers, https://reviewboard.mozilla.org/r/67850/#review64872
Pushed by email@example.com: https://hg.mozilla.org/integration/autoland/rev/f3d6887279f8 Activate the mozharness virtualenv when running tests on interactive workers, r=armenzg