5.39% perf_reftest_singletons parent-basic-singleton.html (Linux) regression on Mon February 3 2025
Categories
(Firefox :: Nimbus Desktop Client, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr128 | --- | unaffected |
| firefox135 | --- | unaffected |
| firefox136 | --- | unaffected |
| firefox137 | --- | affected |
People
(Reporter: intermittent-bug-filer, Unassigned)
References
(Regression)
Details
(4 keywords)
Perfherder has detected a talos performance regression from push ff5432cc7e7c0d223330a7c8f09a89d797793f83. 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) |
|---|---|---|---|---|
| 5% | perf_reftest_singletons parent-basic-singleton.html | linux1804-64-shippable-qr | e10s fission stylo webrender | 104.50 -> 110.13 |
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.
If you need the profiling jobs you can trigger them yourself from treeherder job view or ask a sheriff to do that for you.
You can run all of these tests on try with ./mach try perf --alert 43816
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 fbilt@mozilla.com.
Comment 1•1 year ago
|
||
Set release status flags based on info from the regressing bug 1944677
Comment 2•1 year ago
|
||
Given the changes in that push, I have doubts that this change was caused by my patches -- they essentially move code from one file to another. WONTFIXing this because these changes need to stay.
Description
•