Enable M-fis on tier1
Categories
(Testing :: General, task, P1)
Tracking
(firefox71 fixed)
Tracking | Status | |
---|---|---|
firefox71 | --- | fixed |
People
(Reporter: neha, Assigned: gbrown)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
(deleted),
text/x-phabricator-request
|
Details |
This request is for enabling Mochitests-Fission on Linux 64 debug builds with WebRender on tier1.
Reporter | ||
Updated•5 years ago
|
Assignee | ||
Comment 1•5 years ago
|
||
Should I simply skip all the current failures?
Should mochitest-gpu, mochitest-webgl, mochitest-media be included, or just mochitest-plain?
Reporter | ||
Comment 2•5 years ago
|
||
I believe we need to include Mochitest-plain, mochitest-browser-chrome, mochitest-media, mochitest-webgl.
NI'ing Kris to confirm too.
Assignee | ||
Comment 3•5 years ago
|
||
mochitest-browser-chrome is not normally run on linux64-qr.
Comment 4•5 years ago
|
||
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.
Assignee | ||
Comment 5•5 years ago
|
||
I'm marking high-frequency intermittent failures as blockers. Most of these already have skip-if(fission) patches up for review.
Assignee | ||
Comment 6•5 years ago
|
||
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 7•5 years ago
|
||
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.
Comment 9•5 years ago
|
||
Backed out changeset 666a99f27c23 (Bug 1582881) for high-frequency mochitest failures at test_ext_contentscript_about_blank.html
Backout: https://hg.mozilla.org/integration/autoland/rev/3840361d201f9e7c65e1b0189b7d60c46ebc79e6
Push that started the failures: https://treeherder.mozilla.org/#/jobs?repo=autoland&resultStatus=pending%2Crunning%2Csuccess%2Ctestfailed%2Cbusted%2Cexception&revision=666a99f27c2355c5df34e9302c0c0a70e39a02be&selectedJob=268694082
Failure log: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=268694082&repo=autoland&lineNumber=6397
Comment 10•5 years ago
|
||
Assignee | ||
Comment 11•5 years ago
|
||
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.
Assignee | ||
Comment 12•5 years ago
|
||
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....
Comment 13•5 years ago
|
||
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.
Assignee | ||
Comment 14•5 years ago
|
||
Assignee | ||
Comment 15•5 years ago
|
||
suggests this bug might be able to proceed with the additional manifest updates in bug 1582531 plus additional updates to resolve or skip:
- test_permissions.html (bug 1575185)
- test_navigate_to.html (bug 1580643)
- test_sanitize_domain.html (bug 1584471)
Assignee | ||
Comment 16•5 years ago
|
||
Assignee | ||
Comment 17•5 years ago
|
||
...there are still several intermittents, but none are very high frequency. I'll try landing again.
Comment 18•5 years ago
|
||
Comment 19•5 years ago
|
||
bugherder |
Description
•