Closed Bug 1633327 Opened 5 years ago Closed 5 years ago

72.31% build times (linux64) regression on push 5db725324c27092f4a913c6f6083de446aa48c8d (Thu April 23 2020)

Categories

(Toolkit :: General, defect)

Product:
Toolkit
Component:
General
Type:
defect

Tracking

()

Status:
RESOLVED INVALID
Tracking Flags:
Tracking Status
firefox-esr68 --- unaffected
firefox75 --- unaffected
firefox76 --- unaffected
firefox77 --- wontfix

People

(Reporter: marauder, Unassigned)

References

(Regression)

Details

(Keywords: perf-alert, regression)

Perfherder has detected a 2 performance regression from push 5db725324c27092f4a913c6f6083de446aa48c8d. As author of one of the patches included in that push, we need your help to address this regression.

Regressions:

72% build times linux64 asan opt taskcluster-m5.4xlarge 905.43 -> 1,560.11

Details of the alert can be found in the alert summary, including links to graphs and comparisons for each of the affected tests. Please follow our guide to handling regression bugs and let us know your plans within 3 business days, or the offending patch(es) will be backed out in accordance with our regression policy.

For more information on performance sheriffing please see our FAQ.

Blocks: 1628613
status-firefox75: --- → unaffected
status-firefox76: --- → unaffected
status-firefox77: --- → affected
status-firefox-esr68: --- → unaffected
Component: Performance → General
Flags: needinfo?(emilio)
Product: Testing → Toolkit
Regressed by: 1612068
Version: Version 3 → unspecified
Has Regression Range: --- → yes

I'm confused at the graph, it seems to have recovered later? I don't understand how that push could've potentially caused this regression otherwise, it's just changing a cpp file, so not even touching a common header.

Flags: needinfo?(emilio) → needinfo?(marian.raiciof)

Yes, the graph is very noisy so we can close this as invalid.
Thanks!

Status: NEW → RESOLVED
Closed: 5 years ago
Flags: needinfo?(marian.raiciof)
Resolution: --- → INVALID

Np, thank you for the fast turnaround!

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