Closed
      
        Bug 1489065
      
      
        Opened 7 years ago
          Closed 7 years ago
      
        
    
  
6.61% installer size (osx-cross) regression on push a9caa2a0b5ed5189e945762272e895439aa7b847 (Wed Sep 5 2018) 
    Categories
(Firefox Build System :: General, defect)
        Firefox Build System
          
        
        
      
        
    
        General
          
        
        
      
        
    Tracking
(Not tracked)
        RESOLVED
        WONTFIX
        
    
  
People
(Reporter: jmaher, Unassigned)
References
Details
(Keywords: regression)
We have detected a build metrics regression from push:
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?changeset=a9caa2a0b5ed5189e945762272e895439aa7b847
As author of one of the patches included in that push, we need your help to address this regression.
Regressions:
  7%  installer size osx-cross opt      67,645,845.00 -> 72,119,403.33
You can find links to graphs and comparison views for each of the above tests at: https://treeherder.mozilla.org/perf.html#/alerts?id=15644
On the page above you can see an alert for each affected platform as well as a link to a graph showing the history of scores for this test. There is also a link to a treeherder page showing the jobs in a pushlog format.
To learn more about the regressing test(s), please see: https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Automated_Performance_Testing_and_Sheriffing/Build_Metrics
| Reporter | ||
| Updated•7 years ago
           | 
Product: Testing → Firefox Build System
| Reporter | ||
| Comment 1•7 years ago
           | ||
:glandium, can you confirm that we wanted to increase the installer size by 7% with your change for osx lto builds?
Flags: needinfo?(mh+mozilla)
| Comment 2•7 years ago
           | ||
It's a tradeoff. There should be accompanying (large) perf improvements.
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(mh+mozilla)
Resolution: --- → WONTFIX
| Comment 3•7 years ago
           | ||
That was mentioned in bug 1473786 comment 3, BTW.
          You need to log in
          before you can comment on or make changes to this bug.
        
Description
•