Perfherder has detected a talos performance regression from push 58c2d44671a0f2767146c9f0f1f233cffe8a0736. As author of one of the patches included in that push, we need your help to address this regression.

Regressions:

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 offending patch(es) will be backed out in accordance with our regression policy.

For more information on performance sheriffing please see our FAQ.

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

Too late to fix for 92, but AFAICT this regression is still there on the graphs.

What is the relation between this alert and https://treeherder.mozilla.org/perfherder/alerts?id=30500. That regression seems larger.

Perhaps this was caused by bug 1673511?

I retriggered alert 30500 but the graph is pretty clear to me.

Alexandru, why is 30500 reassigned to 30501? 30500 was from a change on June 21st and 30501 was a change on June 8th.

(In reply to Jeff Muizelaar [:jrmuizel] from comment #3)

What is the relation between this alert and https://treeherder.mozilla.org/perfherder/alerts?id=30500. That regression seems larger.

The regression is later than this and caused by bug 1677253.

(In reply to Jeff Muizelaar [:jrmuizel] from comment #6)

Alexandru, why is 30500 reassigned to 30501? 30500 was from a change on June 21st and 30501 was a change on June 8th.

Yeah, sorry, I reassigned it.

I confirm, this looks like a for real regression caused by https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=58c2d44671a0f2767146c9f0f1f233cffe8a0736

Seems like we've decided to eat this regression at this point.