Open Bug 1550433 Opened 5 years ago Updated 2 years ago

3.63% raptor-tp6-slides-firefox fcp (linux64-shippable-qr) regression on push c078e2cefc3b86e17f1495c13a33aa58dc26be06 (Fri May 3 2019)


(Core :: XPCOM, defect)




Tracking Status
firefox-esr60 --- unaffected
firefox-esr68 --- wontfix
firefox69 --- wontfix
firefox70 --- wontfix
firefox71 --- fix-optional


(Reporter: Bebe, Unassigned)




(Keywords: perf, perf-alert, regression)

Raptor has detected a Firefox performance regression from push:

As author of one of the patches included in that push, we need your help to address this regression.


4% raptor-tp6-slides-firefox fcp linux64-shippable-qr opt 755.62 -> 783.04

You can find links to graphs and comparison views for each of the above tests at:

On the page above you can see an alert for each affected platform as well as a link to a graph showing the history of scores for this test. There is also a link to a Treeherder page showing the Raptor jobs in a pushlog format.

To learn more about the regressing test(s) or reproducing them, please see:

*** Please let us know your plans within 3 business days, or the offending patch(es) will be backed out! ***

Our wiki page outlines the common responses and expectations:

Blocks: 1534654
Component: General → XPCOM
Flags: needinfo?(bugs)
Product: Testing → Core
Regressed by: 1548827
Version: Version 3 → unspecified

Lovely. Because of, this kinds of regressions, or improvements can happen somewhat randomly when changing CC or GC scheduling.
Though, I guess CC might happen there too.
But we really need bug 1543806 fixed.

Flags: needinfo?(bugs)
Has Regression Range: --- → yes
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.