Closed Bug 996049 Opened 10 years ago Closed 10 years ago

ccache enabled in nightly mozconfigs but not beta or release

Categories

(Release Engineering :: Release Automation: Other, defect)

Product:
Release Engineering
Component:
Release Automation: Other
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: bhearsum, Assigned: bhearsum)

Details

Attachments

(1 file)

update whitelist in tools
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)
Also, I wonder why the mozconfig comparisons in "make check" didn't catch this...
--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)
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

        Attachment #8407080 -
        Flags: review?(rail)

    
  
Assignee: nobody → bhearsum

    
  

        Attachment #8407080 -
        Flags: review?(rail) → review+

    
  

        Attachment #8407080 -
        Flags: checked-in+

    
    

    
  
Should be fine for 30.0b1.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED

          You need to log in
          before you can comment on or make changes to this bug.
        






  

    
  







  

    

      
Attachment

      

      
      
      
      
    

    

      

        

          

            
General

            

              Creator: 



            

            
Created: 

            
Updated: 

            
Size: