Closed Bug 1582881 Opened 5 months ago Closed 5 months ago

Enable M-fis on tier1


(Testing :: General, task, P1)

Version 3


(firefox71 fixed)

Tracking Status
firefox71 --- fixed


(Reporter: neha, Assigned: gbrown)


(Blocks 1 open bug)



(1 file)

This request is for enabling Mochitests-Fission on Linux 64 debug builds with WebRender on tier1.

Flags: needinfo?(gbrown)

Should I simply skip all the current failures?

Should mochitest-gpu, mochitest-webgl, mochitest-media be included, or just mochitest-plain?

Assignee: nobody → gbrown
Flags: needinfo?(gbrown)
Priority: -- → P1

I believe we need to include Mochitest-plain, mochitest-browser-chrome, mochitest-media, mochitest-webgl.
NI'ing Kris to confirm too.

Flags: needinfo?(kmaglione+bmo)

We definitely need the bc tests. I don't care much whether they run in QR mode or not, just as long as they run.

We can't include mochitest-gpu, since those are mochitest-chrome tests which run with e10s disabled, and therefore can't enable fission.

We do want media and webgl, though.

Flags: needinfo?(kmaglione+bmo)
Blocks: fission
See Also: → fission-mochitests
Depends on: 1581004
Depends on: 1582999
Depends on: 1582948
Depends on: 1576480

I'm marking high-frequency intermittent failures as blockers. Most of these already have skip-if(fission) patches up for review.

No longer depends on: 1576480, 1581004, 1582948

This changes certain fission tests to run tier 1 and start running on integration branches:
linux64-qr/debug mochitest-plain
linux64-qr/debug mochitest-media
linux64-qr/debug mochitest-webgl*
linux64/debug browser-chrome
All other fission tests continue to run as tier 2 and only on central and try.

No longer depends on: 1582999
Pushed by
Promote select fission tests to tier 1; r=ahal
Depends on: 1575185
Depends on: 1584483
Depends on: 1584471

It looks like there are at least 3 tests that need to be skipped or fixed to proceed. (There may be a couple more, in the dom/push task...need to revisit once these are resolved). These failures were not evident in yesterday's try pushes -- the change is concerning.

Flags: needinfo?(gbrown)

With those 3 tests skipped, test results are better, but there are several other test failures:

I'll try again with the (much appreciated) new patch from bug 1584483....

Bug 1582531 also just landed, which re-enabled a lot of tests which had previously been skipped but now appeared to pass. I think it's unavoidable that some of those will turn out to be intermittent failures that didn't show up in any of our try runs, in which case they should probably be re-skipped with an appropriate comment.

Depends on: 1580643
Depends on: 1576498
Depends on: 1584664
See Also: → 1582531

suggests this bug might be able to proceed with the additional manifest updates in bug 1582531 plus additional updates to resolve or skip:

No longer depends on: 1575185
No longer depends on: 1584471

...there are still several intermittents, but none are very high frequency. I'll try landing again.

No longer depends on: 1576498, 1580643, 1584664
Pushed by
Promote select fission tests to tier 1; r=ahal
Closed: 5 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla71
You need to log in before you can comment on or make changes to this bug.