Closed
Bug 1334209
Opened 6 years ago
Closed 6 years ago
Activate mozharness virtualenv directly from mach commands in one-click loaners
Categories
(Testing :: General, defect)
Testing
General
Tracking
(firefox54 fixed)
RESOLVED
FIXED
mozilla54
Tracking | Status | |
---|---|---|
firefox54 | --- | fixed |
People
(Reporter: ahal, Assigned: ahal)
Details
Attachments
(1 file)
When running the media mochitests (--subsuite=media), we install some extra dependencies in the mach command here: https://dxr.mozilla.org/mozilla-central/source/testing/mochitest/mach_commands.py#343 But we don't install these when running them from the one-click loaner, resulting in a series of ImportErrors. We should also install this from there.
Assignee | ||
Comment 1•6 years ago
|
||
I went to try and reproduce this, and it seemed to work fine for me out of the box. I ran option 2 at the wizard prompt, then `./mach mochitest --subsuite media`. It's mozharness that sets up the websocketprocessbridge_requirements: https://dxr.mozilla.org/mozilla-central/rev/9c06e744b1befb3a2e2fdac7414ce18220774a1d/testing/mozharness/scripts/desktop_unittest.py#312 So choosing option 2 (mozharness setup) should get these dependencies installed into the venv, and option 2 is required to run the mach command in the first place. Paul, do you remember exactly what you took when you were getting those ImportErrors?
Flags: needinfo?(padenot)
Assignee | ||
Comment 2•6 years ago
|
||
*what steps you took
Comment 3•6 years ago
|
||
(In reply to Andrew Halberstadt [:ahal] from comment #1) > I went to try and reproduce this, and it seemed to work fine for me out of > the box. I ran option 2 at the wizard prompt, then `./mach mochitest > --subsuite media`. It's mozharness that sets up the > websocketprocessbridge_requirements: > https://dxr.mozilla.org/mozilla-central/rev/ > 9c06e744b1befb3a2e2fdac7414ce18220774a1d/testing/mozharness/scripts/ > desktop_unittest.py#312 > > So choosing option 2 (mozharness setup) should get these dependencies > installed into the venv, and option 2 is required to run the mach command in > the first place. Paul, do you remember exactly what you took when you were > getting those ImportErrors? I do that multiple times per day currently, and sometimes it works, sometimes it does not work, but activating the venv works. Looks like there is a race somewhere, I don't think I proceed differently when it works and does not work.
Flags: needinfo?(padenot)
Assignee | ||
Comment 4•6 years ago
|
||
Ah, so this is more about a race condition causing the virtualenv not to get activated. The current setup where the venv is sourced by the run-wizard script is fragile. I've been meaning to get the mach bootstrap script to do this in-process anyway, this seems like a good excuse.
Assignee | ||
Updated•6 years ago
|
Summary: Automatically install mochitest media dependencies when running from a one-click loaner → Activate mozharness virtualenv directly from mach commands in one-click loaners
Comment hidden (mozreview-request) |
Comment 6•6 years ago
|
||
mozreview-review |
Comment on attachment 8832578 [details] Bug 1334209 - Activate mozharness virtualenv in-process from one click loaner mach commands, https://reviewboard.mozilla.org/r/108792/#review110028 rubber stamp=me
Attachment #8832578 -
Flags: review?(jmaher) → review+
Assignee | ||
Updated•6 years ago
|
Assignee: nobody → ahalberstadt
Status: NEW → ASSIGNED
Pushed by ahalberstadt@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/d70a7e18fe84 Activate mozharness virtualenv in-process from one click loaner mach commands, r=jmaher
Comment 8•6 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/d70a7e18fe84
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
status-firefox54:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla54
You need to log in
before you can comment on or make changes to this bug.
Description
•