1.33 - 1.43% installer size (windows2012-32, windows2012-64) regression on push b21ad1316ba60537d00e99fa89951580802c963b (Tue Sep 12 2017)

RESOLVED INVALID

Status

()

Core
Networking: JAR
RESOLVED INVALID
10 months ago
10 months ago

People

(Reporter: igoldan, Unassigned)

Tracking

(Blocks: 1 bug, {regression})

Firefox Tracking Flags

(Not tracked)

Details

We have detected a build metrics regression from push:

https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?changeset=b21ad1316ba60537d00e99fa89951580802c963b

As author of one of the patches included in that push, we need your help to address this regression.

Regressions:

  1%  installer size summary windows2012-32 pgo      54,535,711.58 -> 55,315,175.58
  1%  installer size summary windows2012-64 pgo      58,627,091.50 -> 59,406,598.67

Improvements:

  2%  installer size summary linux64 pgo      63,674,708.00 -> 62,318,941.83
  2%  installer size summary linux32 pgo      64,707,294.25 -> 63,348,582.17
  1%  installer size summary osx-cross opt    66,363,190.00 -> 65,645,491.67


You can find links to graphs and comparison views for each of the above tests at: https://treeherder.mozilla.org/perf.html#/alerts?id=9387

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
Component: Untriaged → Networking: JAR
Product: Firefox → Core
Mike, I see the backout caused these regressions on Windows. Can these be addressed?
Flags: needinfo?(mh+mozilla)

Comment 2

10 months ago
See bug 1352595 comment 27. The windows installer sizes are measuring the wrong thing.
Status: NEW → RESOLVED
Last Resolved: 10 months ago
Flags: needinfo?(mh+mozilla)
Resolution: --- → INVALID
Thanks for correcting this.
You need to log in before you can comment on or make changes to this bug.