Closed
Bug 996049
Opened 11 years ago
Closed 11 years ago
ccache enabled in nightly mozconfigs but not beta or release
Categories
(Release Engineering :: Release Automation, defect)
Release Engineering
Release Automation
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Assigned: bhearsum)
Details
Attachments
(1 file)
|
758 bytes,
patch
|
rail
:
review+
bhearsum
:
checked-in+
|
Details | Diff | Splinter Review |
Noticed this while doing a staging release for 30.0. I think we probably want to enable it everywhere, so we should put ". $topsrcdir/build/mozconfig.cache" in the common-opt mozconfigs?
Flags: needinfo?(mh+mozilla)
|
Assignee | |
Comment 1•11 years ago
|
||
Also, I wonder why the mozconfig comparisons in "make check" didn't catch this...
|
||
Comment 2•11 years ago
|
||
--with-ccache was never there to begin with. And I think it's a good thing. Avoids any problem that might come from using ccache or sccache.
Flags: needinfo?(mh+mozilla)
|
|
Assignee | |
Comment 3•11 years ago
|
||
Turns out the whitelist is duplicated in a releng repo still. Probably because we don't have it in tree for android and thunderbird yet...
Component: Build Config → Release Automation
Product: Firefox → Release Engineering
QA Contact: bhearsum
|
|
Assignee | |
Comment 4•11 years ago
|
||
Attachment #8407080 -
Flags: review?(rail)
|
|
Assignee | |
Updated•11 years ago
|
Assignee: nobody → bhearsum
|
||
Updated•11 years ago
|
Attachment #8407080 -
Flags: review?(rail) → review+
|
|
Assignee | |
Updated•11 years ago
|
Attachment #8407080 -
Flags: checked-in+
|
|
Assignee | |
Comment 5•11 years ago
|
||
Should be fine for 30.0b1.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•