Closed
Bug 1385744
Opened 7 years ago
Closed 7 years ago
build-clang.py doesn't handle the llvm source cache properly
Categories
(Firefox Build System :: General, enhancement)
Firefox Build System
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: glandium, Assigned: glandium)
Details
Attachments
(1 file)
Windows clang-cl builds are using a llvm source cache, presumably to make the build faster, but it fails to use it properly, leading to surprising results. Most notably, if one tries to push a different branch than trunk and hit the cache, the result will still be from the trunk branch, because the svn update calls just update to the revision without doing anything about the repo url.
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → mh+mozilla
Comment hidden (mozreview-request) |
Comment 2•7 years ago
|
||
mozreview-review |
Comment on attachment 8892862 [details] Bug 1385744 - Stop using a cache for the llvm source. https://reviewboard.mozilla.org/r/163876/#review169376 Caches are one of the hardest problems in computer science!
Attachment #8892862 -
Flags: review?(gps) → review+
Pushed by mh@glandium.org: https://hg.mozilla.org/mozilla-central/rev/22ad2f44b6f8 Stop using a cache for the llvm source. r=gps
Assignee | ||
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Core → Firefox Build System
You need to log in
before you can comment on or make changes to this bug.
Description
•