1909338 - 2.15 - 1.65% tart / tart (Windows) regression on Tue July 9 2024

Status: NEW

(Firefox :: Theme, defect, P2)

Description

[Andrej (:aglavic)]

Perfherder has detected a talos performance change from push e46eaccd15b497f7694c9f16e80815d380f2e96b.

Regressions:

Ratio	Test	Platform	Options	Absolute values (old vs new)
2%	tart	windows11-64-qr	e10s fission stylo webrender	2.17 -> 2.21
2%	tart	windows11-64-qr	e10s fission stylo webrender	2.17 -> 2.21

As author of one of the patches included in that push, we need your help to address this regression.
Details of the alert can be found in the alert summary, including links to graphs and comparisons for each of the affected tests. Please follow our guide to handling regression bugs and let us know your plans within 3 business days, or the patch(es) may be backed out in accordance with our regression policy.

If you need the profiling jobs you can trigger them yourself from treeherder job view or ask a sheriff to do that for you.

You can run these tests on try with ./mach try perf --alert 1402

For more information on performance sheriffing please see our FAQ.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

Set release status flags based on info from the regressing bug 1881851

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

Set release status flags based on info from the regressing bug 1881851

Comment 3

[Daniel Holbert [:dholbert]]

The Ratio | 2% links in comment 0 just trigger a PerfHerder error page for me, with "Something went wrong TypeError: can't access property "y", e[0] is undefined". That's bug 1855574 -- I've just added a note there.

The broken URL is:
https://treeherder.mozilla.org/perfherder/graphs?timerange=1209600&series=autoland,81652,1,1

If I instead click through to comment 0's alert summary and then click the graph, I end up with a similar URL that does work properly (it renders a graph):
https://treeherder.mozilla.org/perfherder/graphs?timerange=5184000&series=autoland,81652,1,1

However, that^ graph shows the data points ending on Jul 19, and no data at all for the past month (from Jul 19 up to today, Aug 19).

aglavic, do you know what's going on? Did we discontinue testing this particular configuration or something?

Comment 4

[Andrej (:aglavic)]

Hey :dholbert, sorry for the delay
Took a while but I figured out why the issue hapened, I've updated comment 0 and the link should work.
I'll update our sheriffs to ensure this does not happen again thank you for being patient

Comment 5

[Daniel Holbert [:dholbert]]

Thanks! The link works now, but it still shows the data ending on Jul 19, per end of comment 3 -- do you know what's causing that? Is this a configuration that we discontinued or something?

Comment 6

[Andrej (:aglavic)]

I apologize, I was too focused on the broken link and missed your comment about the data ending on July 19
So to answer your question 2 things happened in tandem which created this
1 Adding the windows11 tests, and 2 migrating out to shippable
There was a month period where we added windows11, and then removed the -qr with -shippable-qr
The tests are still running and you can find them here: https://treeherder.mozilla.org/perfherder/graphs?highlightAlerts=1&highlightChangelogData=1&highlightCommonAlerts=0&replicates=0&selected=86450,42527019&series=autoland,86450,1,1&timerange=31536000

Comment 7

[Daniel Holbert [:dholbert]]

Thanks! That makes sense.