Closed
Bug 1718156
Opened 3 years ago
Closed 3 years ago
Avoid some configure tests creating the common virtualenv
Categories
(Firefox Build System :: General, task)
Firefox Build System
General
Tracking
(firefox91 fixed)
RESOLVED
FIXED
91 Branch
Tracking | Status | |
---|---|---|
firefox91 | --- | fixed |
People
(Reporter: glandium, Assigned: glandium)
References
Details
Attachments
(1 file)
No description provided.
Assignee | ||
Comment 1•3 years ago
|
||
When running mach python-test
on a clobbered tree, we create both the
python-test and common virtualenvs, but the former should be enough. The
latter is only created when running tests that use the BaseConfigureTest
class, when it indirectly includes init.configure, which makes the
configure sandbox run the virtualenv_python3 function, which ends up
initializing the common virtualenv. We only don't end up re-executing
that virtualenv python thanks to 6680ca0acc27 which was a workaround
that would allow any virtualenv in $objdir/_virtualenvs, while still
creating a virtualenv it won't use.
Tests now tell virtualenv_python3 to not use the normal virtualenv
manager, and remove the workaround.
Pushed by mh@glandium.org: https://hg.mozilla.org/integration/autoland/rev/3e7432adb765 Avoid some configure tests creating the common virtualenv. r=firefox-build-system-reviewers,mhentges,andi
Comment 3•3 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 3 years ago
status-firefox91:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 91 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•