Talos has detected a Firefox performance regression from push 9ad182a8983188fa58876f8d349e3446b9dc4fd4. As author of one of the patches included in that push, we need your help to address this regression. Regressions: 3% tabpaint summary linux64 pgo 68.31 -> 70.69 You can find links to graphs and comparison views for each of the above tests at: https://treeherder.mozilla.org/perf.html#/alerts?id=5566 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 → DOM: Events
Product: Firefox → Core
Target Milestone: --- → mozilla55
I don't really understand how you decided this was the result of that specific push. I see retriggers on the graph https://treeherder.mozilla.org/perf.html#/graphs?series=%5Bmozilla-inbound,c0d928c1e60b5975297a402af4156d9340a13a1d,1,1%5D&series=%5Bautoland,c0d928c1e60b5975297a402af4156d9340a13a1d,1,1%5D&selected=%5Bautoland,c0d928c1e60b5975297a402af4156d9340a13a1d,183720,85718279,1%5D for my push and some inbound stuff, which isn't really enough to pinpoint a random autoland push. My push was a backout with a small addition specific to about:preferences (which doesn't affect tabpaint), and there was no corresponding change when the original bug landed, so I don't see how this would have caused a regression like this. It looks to me like more tracking is needed to figure out which bug caused the change here.
Thank you for your insights! I'm taking a closer look over the alert.
:Gijs You are right. Changeset 9ad182a89831 didn't do any regression. A closer look over this revealed that the alerts got triggered by 2 PGO artifacts, on linux64 and windows7. You can see it better here: https://treeherder.mozilla.org/perf.html#/graphs?series=%5Bautoland,6ed576324fb267354c6c2830e9373700a0682208,1,1%5D&series=%5Bautoland,5ff79f1f47feb31b810f52e56b428aca29eab389,1,1%5D&series=%5Bautoland,e450cf30f075279a05fd11783ab56e64982501e6,1,1%5D&series=%5Bautoland,83966baaedd49645f0ebb0185077f032ba1d8a72,1,1%5D&series=%5Bautoland,55d3374127db018f6a1943b7044f992395ced9eb,1,1%5D&highlightedRevisions=55b8f2772d01&highlightedRevisions=9ad182a89831 Thank you for your quick notice!
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INVALID
thanks igoldan for investigating this.
You need to log in before you can comment on or make changes to this bug.