0.75 - 1.81% Base Content JS (linux1804-64-shippable, linux1804-64-shippable-qr, macosx1014-64-shippable, windows10-64-shippable-qr, windows7-32-shippable) regression on push 840f993400695f8c67d44b35f5f7f4b2c4bcf5fd (Wed July 15 2020)
Categories
(Testing :: Performance, defect, P3)
Tracking
(firefox-esr68 unaffected, firefox-esr78 unaffected, firefox78 unaffected, firefox79 unaffected, firefox80 wontfix)
Tracking | Status | |
---|---|---|
firefox-esr68 | --- | unaffected |
firefox-esr78 | --- | unaffected |
firefox78 | --- | unaffected |
firefox79 | --- | unaffected |
firefox80 | --- | wontfix |
People
(Reporter: Bebe, Unassigned)
References
(Regression)
Details
(Keywords: perf, perf-alert, regression)
Perfherder has detected a awsy performance regression from push 5ab89a7196a366cbf79c7e99d40cf6b7b869fe31. As author of one of the patches included in that push, we need your help to address this regression.
Regressions:
2% Base Content JS macosx1014-64-shippable opt 3,485,696.83 -> 3,548,873.00
1% Base Content JS windows7-32-shippable opt 2,731,551.67 -> 2,756,862.00
1% Base Content JS linux1804-64-shippable opt 3,480,115.67 -> 3,509,017.67
1% Base Content JS linux1804-64-shippable-qr opt 3,480,093.00 -> 3,508,980.33
1% Base Content JS windows10-64-shippable-qr opt 3,545,770.67 -> 3,572,493.33
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.
Reporter | ||
Comment 1•4 years ago
|
||
I can't backfill through these 3 bugs can you help determine who generated this regression?
Comment 2•4 years ago
|
||
My patch got backed out so I don't think my patch could have caused this.
Comment 3•4 years ago
|
||
This is likely caused by my patch as it adds self-hosted JS, which has caused similar regressions in the past (i.e. https://bugzilla.mozilla.org/show_bug.cgi?id=1644430).
Comment 4•4 years ago
|
||
Bug 1649311 only touched C++ code so it seems unlikely that it would have caused a Base Content JS regression.
Updated•4 years ago
|
Comment 5•4 years ago
|
||
Set release status flags based on info from the regressing bug 1647796
Comment 6•4 years ago
|
||
Since this was caused by my patch, this is expected due to the additional self-hosted JS.
Updated•4 years ago
|
Description
•