Talos has detected a Firefox performance regression from push f328ac32af6a. As author of one of the patches included in that push, we need your help to address this regression. This is a list of all known regressions and improvements related to the push: https://treeherder.mozilla.org/perf.html#/alerts?id=1017 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#Dromaeo_Tests https://wiki.mozilla.org/Buildbot/Talos/Tests#tabpaint Reproducing and debugging the regression: If you would like to re-run this Talos test on a potential fix, use try with the following syntax: try: -b o -p macosx64,win64 -u none -t svgr-e10s[10.10,Windows 8],dromaeojs-e10s[10.10,Windows 8],other[10.10,Windows 8] --rebuild 5 # add "mozharness: --spsProfile" to generate profile data (we suggest --rebuild 5 to be more confident in the results) To run the test locally and do a more in-depth investigation, first set up a local Talos environment: https://wiki.mozilla.lorg/Buildbot/Talos/Running#Running_locally_-_Source_Code Then run the following command from the directory where you set up Talos: talos --develop -e [path]/firefox -a dromaeo_css:tabpaint (add --e10s to run tests in e10s mode) Making a decision: As the patch author we need your feedback to help us handle this regression. Our wiki page outlines the common responses and expectations: https://wiki.mozilla.org/Buildbot/Talos/RegressionBugsHandling
this only seemed to affect aurora when it landed there and is now on beta! :nical, can you investigate this and determine why this is happening?
Component: Untriaged → Graphics: Layers
Product: Firefox → Core
oh, I am sorry- I thought I had collected more data and realized that this is related to the uplift, not this patch.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.