0.43% installer size (OSX) regression on Wed December 18 2024
Categories
(Core :: DOM: Security, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr128 | --- | unaffected |
firefox133 | --- | unaffected |
firefox134 | --- | unaffected |
firefox135 | --- | wontfix |
People
(Reporter: intermittent-bug-filer, Unassigned)
References
(Regression)
Details
(Keywords: perf-alert, regression)
Perfherder has detected a build_metrics performance regression from push 2e1c3fe92eea5b1ba8526e14f4c2961c8e9e0676. 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) |
---|---|---|---|---|
0.43% | installer size | osx-shippable | nightly | 102,579,795.12 -> 103,016,602.50 |
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 patch(es) may be backed out in accordance with our regression policy.
You can run all of these tests on try with ./mach try perf --alert 43139
The following documentation link provides more information about this command.
For more information on performance sheriffing please see our FAQ.
If you have any questions, please do not hesitate to reach out to afinder@mozilla.com.
Updated•2 months ago
|
Comment 1•2 months ago
|
||
Set release status flags based on info from the regressing bug 1900537
Comment 2•2 months ago
|
||
No action needed. This regression is expected, has been discussed, and has been minimized already (through removing all external crypto dependencies and spending a lot of time re-plugging everything on top of NSS).
Comment 3•2 months ago
|
||
Marking as fixed for 135 based on the above comment. Thanks!
Updated•1 months ago
|
Description
•