Closed
Bug 1209112
Opened 9 years ago
Closed 2 years ago
Virtualenv cache always gets clobbered
Categories
(Release Engineering :: Applications: MozharnessCore, defect)
Release Engineering
Applications: MozharnessCore
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: armenzg, Unassigned)
References
(Blocks 1 open bug)
Details
I wonder how caching should work when we modify mozbase packages on the push. We would need to have a way to use the package in the test.zip or not. catlee: what do you think? Looking only at mochitest jobs. Desktop jobs: * Linux [1] * Mac [2] * Windows [3] Mobile jobs: * Android [4] [1] Creating supposed download cache at /builds/slave/test/build/venv/cache [2] Creating supposed download cache at /builds/slave/test/build/venv/cache [3] Creating supposed download cache at C:\slave\test\build\venv\cache [4] Creating supposed download cache at /builds/slave/test/build/venv/cache
Reporter | ||
Comment 1•9 years ago
|
||
Also see: Bug 1213052 - Analyze what we could improve in the virtualenv action
Reporter | ||
Comment 2•9 years ago
|
||
Kyle, I'm trying to figure out what is the percentage that "create-virtualenv" on average takes from each pool, however, my initial query is failing. http://activedata.allizom.org/tools/query.html#query_id=zh+iWJxg "caused by Where clause is too deep"
Updated•2 years ago
|
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•