Windows workers use the wrong path for checkout cache
Categories
(Firefox Build System :: Task Configuration, task)
Tracking
(Not tracked)
People
(Reporter: glandium, Unassigned)
References
Details
Attachments
(1 file)
(deleted),
text/x-phabricator-request
|
Details |
Reporter | ||
Updated•6 years ago
|
Reporter | ||
Comment 1•6 years ago
|
||
On docker-worker and mac, checkout caches are in a separate directory
from the workspace. It also happens that the current setup makes the
checkout caches actually unused, and that's a good thing, considering
builds happening on docker-worker currently fill the source directory
with build artifacts.
However, on Windows, the current setup is such that the source directory
and build artifacts are all part of the checkout cache location, which,
if caches were enabled, would make all windows builds share their
objdir, which would not work quite well when building e.g. beta after
central, or debug after opt, for that matter (since all build types
share checkout caches).
As a matter of fact, one reason enabling caches failed is that because
the objdir is part of the directory, the size of the data to be cached
was tremendous.
Reporter | ||
Comment 2•6 years ago
|
||
Considering the mess there is to untangle to fix this, and my todo list, I won't be putting more time into this.
Comment 3•5 years ago
|
||
This ended up being fixed as part of Bug 1519472.
Comment 4•5 years ago
|
||
Actually in Bug 1527313.
Description
•