171.54% compiler warnings (Windows) regression on Tue April 9 2024
Categories
(Core :: Networking, defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox125 | --- | unaffected |
firefox126 | --- | wontfix |
firefox127 | --- | fixed |
People
(Reporter: afinder, Assigned: jesup)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: perf-alert, regression, Whiteboard: [necko-triaged])
Attachments
(1 file)
Perfherder has detected a build_metrics performance regression from push ac55c45e0d0f78544391702bda11cab09c0e60b0. 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) |
---|---|---|---|---|
172% | compiler warnings | windows2012-64-shippable | nightly | 490.17 -> 1,331.00 |
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 these tests on try with ./mach try perf --alert 42206
For more information on performance sheriffing please see our FAQ.
Comment 1•1 month ago
|
||
Set release status flags based on info from the regressing bug 1871963
Assignee | ||
Updated•1 month ago
|
Comment 2•1 month ago
|
||
Could this be triaged for severity?
Setting Fx126 as optional since it's not a user issue and Fx126 is now in beta
Wondering if a fix will be prioritized for fx127 at least or later?
Comment 3•28 days ago
|
||
It's probably not easy to fix since I assume those warnings are from the 3rd party library.
Comment 4•28 days ago
|
||
:jesup, since you are the author of the regressor, bug 1871963, could you take a look?
For more information, please visit BugBot documentation.
Updated•27 days ago
|
Assignee | ||
Comment 5•27 days ago
|
||
I'll see if we can add something to suppress the warning in the external zstd library
Updated•19 days ago
|
Comment 7•17 days ago
|
||
I guess we could remove these flags here - if we think these warnings are really meant to be suppressed. Otherwise we can WONTFIX it?
Updated•17 days ago
|
Comment 8•11 days ago
|
||
It's a LOT of warning spam in the console (which I believe can actually impact build times as well). We should not WONTFIX this bug and I hope we can prioritize fixing it soon.
Assignee | ||
Comment 9•10 days ago
|
||
Updated•10 days ago
|
Comment 10•10 days ago
|
||
Pushed by rvandermeulen@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/ef3141d05710 remove -Wall from zstd compile options (windows dislikes it) r=necko-reviewers,valentin
Assignee | ||
Updated•10 days ago
|
Comment 11•10 days ago
|
||
bugherder |
Description
•