Closed Bug 1604459 Opened 4 years ago Closed 4 years ago

8.52% build times (linux64-shippable) regression on push 051d03569da837849125bda0297cd776cb5ccbb5 (Tue December 3 2019)

Categories

(Firefox Build System :: General, defect)

defect
Not set
normal

Tracking

(firefox73 wontfix)

RESOLVED WONTFIX
mozilla73
Tracking Status
firefox73 --- wontfix

People

(Reporter: marauder, Unassigned)

References

(Regression)

Details

(Keywords: perf-alert, regression)

We have detected a build metrics regression from push:

https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=051d03569da837849125bda0297cd776cb5ccbb5

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

Regressions:

9% build times linux64-shippable opt nightly taskcluster-m5.4xlarge 2,844.17 -> 3,086.40

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

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

*** Please let us know your plans within 3 business days, or the offending patch(es) will be backed out! ***

The data point that caused the regression is a merge between mozilla-central and autoland.

After i investigated the bugs and comments, i think this is related to
https://bugzilla.mozilla.org/show_bug.cgi?id=1595218

Blocks: 1600879
Status: NEW → RESOLVED
Closed: 4 years ago
Component: Performance → General
Product: Testing → Firefox Build System
Regressed by: 1595218
Resolution: --- → INCOMPLETE
See Also: → 1595218
Target Milestone: --- → mozilla73
Version: Version 3 → unspecified
Has Regression Range: --- → yes
Status: RESOLVED → REOPENED
Flags: needinfo?(cmanchester)
Resolution: INCOMPLETE → ---
See Also: 1595218

I think we need to accept this. If I increase the time scale on those graphs it's not clear to me this persisted past the final re-landing of that bug.

Flags: needinfo?(cmanchester)

Thanks Chris!
I'll mark it as won't fix.

Status: REOPENED → RESOLVED
Closed: 4 years ago4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.