Closed Bug 1870069 Opened 6 months ago Closed 6 months ago

3.09% tart (OSX) regression on Sun December 3 2023

Categories

(Core :: Widget: Cocoa, defect)

defect

Tracking

()

RESOLVED DUPLICATE of bug 1869853
Tracking Status
firefox-esr115 --- unaffected
firefox120 --- unaffected
firefox121 --- unaffected
firefox122 --- affected

People

(Reporter: aglavic, Unassigned)

References

(Regression)

Details

(4 keywords)

Perfherder has detected a talos performance regression from push 13625780fe78d4492e22db961ada61dafaf7b7e8. 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)
3% tart macosx1015-64-shippable-qr e10s fission stylo webrender-sw 2.59 -> 2.67
3% tart macosx1015-64-shippable-qr e10s fission stylo webrender-sw 2.58 -> 2.66

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.

For more information on performance sheriffing please see our FAQ.

Set release status flags based on info from the regressing bug 1867659

:emilio, since you are the author of the regressor, bug 1867659, could you take a look? Also, could you set the severity field?

For more information, please visit BugBot documentation.

I think this is basically bug 1869853 and graph seems to agree, can you confirm? Thanks!

Flags: needinfo?(emilio) → needinfo?(aglavic)

yes I see the future commit that looks to have reversed the regression back to the norm.
I will let you close this with the appropriate resolution

Flags: needinfo?(aglavic)
Status: NEW → RESOLVED
Closed: 6 months ago
Duplicate of bug: 1869853
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.