1624787 - 0.32 - 0.33% Base Content JS (linux1804-64-shippable, linux1804-64-shippable-qr, macosx1014-64-shippable, windows10-64-shippable, windows10-64-shippable-qr) regression on push 2ca9d49fdbf9e8499deba1b6a0a66ea72926d446 (Mon March 23 2020)

Status: NEW

(Core :: DOM: Core & HTML, defect, P3)

Description

[Alexandru Ionescu (needinfo me) [:alexandrui]]

We have detected an awsy regression from push:

https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=2ca9d49fdbf9e8499deba1b6a0a66ea72926d446

As author of one of the patches included in that push, we need your help to address this regression.

Regressions:

0.33% Base Content JS linux1804-64-shippable opt 3,785,496.00 -> 3,797,855.33
0.33% Base Content JS linux1804-64-shippable-qr opt 3,785,390.00 -> 3,797,793.33
0.33% Base Content JS windows10-64-shippable opt 3,852,445.33 -> 3,864,979.33
0.32% Base Content JS macosx1014-64-shippable opt 3,787,506.67 -> 3,799,786.00
0.32% Base Content JS windows10-64-shippable-qr opt 3,852,468.67 -> 3,864,756.00
0.32% Base Content JS windows10-64-shippable-qr opt 3,852,519.33 -> 3,864,818.67

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

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 jobs in a pushlog format.

To learn more about the regressing test(s), please see: https://wiki.mozilla.org/AWSY/Tests

Comment 1

[Andrea Marchesini [:baku]]

Audioworklets are disabled by pref and they are enabled in nightly only. Is this regression in release or nightly?

Comment 2

[Florin Strugariu [:Bebe]]

tests are run on autoland.
So I would say the regression is on Nightly

Comment 3

[Hsin-Yi Tsai (she/her) [:hsinyi]]

Base on comment 1 and comment 2, set firefox76-status as disabled.

Comment 4

[Firefox Bug Husbandry Bot]

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is P3 (Backlog,) indicating it has been triaged, the bug's Severity is being updated to S3 (normal.)