Closed
Bug 1441538
Opened 7 years ago
Closed 7 years ago
3.09 - 15.38% damp (linux64, osx-10-10, windows10-64, windows7-32) regression on push c1d4e29c9e3bb8ab502df0ad53b0e396418212aa (Mon Feb 26 2018)
Categories
(DevTools :: Inspector, defect)
DevTools
Inspector
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: igoldan, Unassigned)
References
Details
(Keywords: perf, regression, talos-regression)
Talos has detected a Firefox performance regression from push:
https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=c1d4e29c9e3bb8ab502df0ad53b0e396418212aa
As author of one of the patches included in that push, we need your help to address this regression.
Regressions:
15% damp windows7-32 opt e10s stylo 60.32 -> 69.59
10% damp windows10-64 opt e10s stylo 54.13 -> 59.49
6% damp linux64 opt e10s stylo 49.92 -> 53.07
4% damp osx-10-10 opt e10s stylo 87.77 -> 91.54
3% damp linux64 pgo e10s stylo 46.84 -> 48.29
You can find links to graphs and comparison views for each of the above tests at: https://treeherder.mozilla.org/perf.html#/alerts?id=11786
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 Talos jobs in a pushlog format.
To learn more about the regressing test(s), please see: https://wiki.mozilla.org/Buildbot/Talos/Tests
For information on reproducing and debugging the regression, either on try or locally, see: https://wiki.mozilla.org/Buildbot/Talos/Running
*** 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: https://wiki.mozilla.org/Buildbot/Talos/RegressionBugsHandling
Reporter | ||
Comment 1•7 years ago
|
||
Marking this as WONTFIX, as stated here https://bugzilla.mozilla.org/show_bug.cgi?id=1432416#c28
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
Updated•6 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•