Closed Bug 1347675 Opened 3 years ago Closed 3 years ago

17.01% tabpaint (windows7-32) regression on push 78b008fb7d12ac75b2ad06d06ab65e6bc4ae8bb5 (Tue Mar 14 2017)

Categories

(Testing :: Marionette, defect)

53 Branch
defect
Not set

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: rwood, Assigned: ato)

Details

(Keywords: perf, regression, talos-regression)

Talos has detected a Firefox performance regression from push 78b008fb7d12ac75b2ad06d06ab65e6bc4ae8bb5. As author of one of the patches included in that push, we need your help to address this regression.

Regressions:

 17%  tabpaint summary windows7-32 opt e10s     60.54 -> 70.84


You can find links to graphs and comparison views for each of the above tests at: https://treeherder.mozilla.org/perf.html#/alerts?id=5471

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
Component: Untriaged → Marionette
Product: Firefox → Testing
This change is just to an assert, I am really shocked that this would cause the issue. The change is in https://hg.mozilla.org/integration/autoland/rev/78b008fb7d12ac75b2ad06d06ab65e6bc4ae8bb5
Thanks for letting me know - apologies, I should have retriggered the talos jobs on the commits before and after (not just on the alerting one). Please disregard, closing as invalid.
No longer blocks: 1346783, 1340775
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.