Closed Bug 1698849 Opened 4 years ago Closed 4 years ago

Avoid mochitest chrome/a11y in TV with Fission

Categories

(Testing :: General, defect, P2)

Default
defect

Tracking

(firefox-esr78 unaffected, firefox86 unaffected, firefox87 unaffected, firefox88 fixed)

RESOLVED FIXED
88 Branch
Tracking Status
firefox-esr78 --- unaffected
firefox86 --- unaffected
firefox87 --- unaffected
firefox88 --- fixed

People

(Reporter: ahal, Assigned: gbrown)

References

(Regression)

Details

(Keywords: regression)

Attachments

(1 file)

In bug 1689061 we stood up some fission test-verify tasks. However, when a mochitest chrome or a11y task is modified, TV will automatically disable e10s (as those suites don't support e10s). However fission requires e10s, so we get failures like the one in bug 1698008.

It looks like mozharness is responsible for selecting TV suites here:
https://searchfox.org/mozilla-central/source/testing/mozharness/mozharness/mozilla/testing/per_test_base.py#454

So I guess we need some logic there to avoid mochitest-a11y and mochitest-chrome when the task will be running with Fission

In the past I have tried to keep to the strategy: "Only enable TV on a platform when all TV-supported suites are supported on that platform." But this seems like a reasonable exception.

If possible, I would like to avoid selecting chrome/a11y tests during find_misc_tests(), when running against fission; I can have a look at that.

Assignee: nobody → whole.grains
Severity: -- → S2

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

Pushed by whole.grains@protonmail.com: https://hg.mozilla.org/integration/autoland/rev/3d3c707bc200 Avoid TV-fis failure for mochitest-chrome/a11y; r=jmaher
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → 88 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: