0.69 - 0.3% installer size / installer size + 2 more (OSX) regression on Tue November 2 2021
Categories
(Core :: WebRTC, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr91 | --- | unaffected |
firefox94 | --- | unaffected |
firefox95 | --- | unaffected |
firefox96 | --- | wontfix |
People
(Reporter: aesanu, Unassigned)
References
(Regression)
Details
(Keywords: perf-alert, regression)
Perfherder has detected a build_metrics performance regression from push 751a117c658f9039c0fe64fef0797ad1544ff216. As author of one of the patches included in that push, we need your help to address this regression.
Regressions:
Ratio | Test | Platform | Options | Absolute values (old vs new) |
---|---|---|---|---|
1% | installer size | osx-shippable | instrumented | 114,784,742.92 -> 115,577,401.08 |
0.39% | installer size | osx-cross | 78,851,421.75 -> 79,160,169.67 | |
0.35% | installer size | osx-aarch64-shippable | aarch64 nightly | 78,580,463.25 -> 78,858,621.92 |
0.30% | installer size | osx-shippable | nightly | 81,222,532.50 -> 81,466,305.67 |
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.
Comment 1•3 years ago
|
||
Given the size of bug 1654112, and all the code it updated (just look at the one commit that updated the upstream libwebrtc), this seems perfectly reasonable.
Comment 2•3 years ago
|
||
Set release status flags based on info from the regressing bug 1654112
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Description
•