Enable Fission mochitest-media-gli tests on more platforms
Categories
(Testing :: Mochitest, task)
Tracking
(Fission Milestone:M7a, firefox-esr78 wontfix, firefox86 wontfix, firefox87 wontfix, firefox88 wontfix, firefox89 fixed)
People
(Reporter: cpeterson, Assigned: bryce)
References
(Blocks 1 open bug)
Details
Attachments
(5 files)
Our testing strategy and list of tests we'd like to enable on which platforms:
https://docs.google.com/document/d/19MergQfMob2mdb_s7hlz5Ilj7Bn-Bbi324r6d2bZfxw/edit
We want to run these tests on:
- debug and opt builds
- Where “shippable” opt builds available, we prefer to test shippable opt builds on central and plain opt builds on autoland.
- autoland and central
- We prefer to run tests with Fission + WebRender (“qr”) where available.
We should probably enable the Fission mochitest-media tests in bug 1694828 before enabling these mochitest-media-gli tests.
Add platforms:
- linux1804-64-qr/debug
- linux1804-64-qr/opt on autoland, shippable-qr opt on central
- linux1804-64-asan/opt
- linux1804-64-tsan/opt
- windows10-64-qr/debug
- windows10-64-qr/opt on autoland, shippable-qr opt on central
Comment 2•4 years ago
|
||
These tests should be enabled latest by M7a milestone (the sooner the better so we can find and fix problems sooner).
Updated•4 years ago
|
Reporter | ||
Comment 3•4 years ago
|
||
Assigning remaining "Enable Fission tests on more platforms" bugs to ahal.
Comment 4•4 years ago
|
||
This bug has been added to releng's backlog and will be picked up sometime in the next few weeks. I'll likely end up taking this, but unassigning myself for now in case someone else ends up helping out.
Assignee | ||
Comment 5•4 years ago
|
||
Putting my name down here as as the media person to ping if issues come up. I can also look at enabling these myself and marking issues, but I'm not clear on which config needs to change to enable the gli test specifically.
Comment 6•4 years ago
|
||
I could use the help and would be willing to teach you how to enable these tasks :)
This one is a bit trickier than the others since it is combining two variants. But maybe I can put up an initial patch that sorts that out and would make following patches to enable the tasks trivial.. I'll put up the prerequisite patch here either way.
Comment 7•4 years ago
|
||
Updated•4 years ago
|
Comment 8•4 years ago
|
||
Bryce, with the attached patch (which can land as soon as it's reviewed) you'll be able to run these tasks via e.g ./mach try fuzzy --full -q "'mochitest-media-fis-gli"
If you're interested in picking this bug up I'd appreciate it! Basically just modify the run-on-projects
line in my patch from:
fission-webgl-ipc: []
to something like:
fission-webgl-ipc:
by-test-platform:
(linux.*64|windows10-64)-qr/debug: ['autoland', 'mozilla-central']
default: []
The above would run the fis-gli
tasks on linux and Windows debug with webrender enabled. The by-test-platform
key is kind of like a case statement where the task will receive the value from whichever regex it first matches. You'll need to add more regexes than in my example to fulfill the request in this bug.
To see a diff of how your change affects the taskgraph, you can run:
$ ./mach taskgraph target --target-kind test --fast --diff .~1 -p project=autoland
Substitute autoland
with mozilla-central
to see the impacts your change has there instead. Beware that using --diff
will update your working directory (it will abort if working directory is dirty). Also note that if you are modifying anything other than the run-on-projects
key, you should also pass in -J
(without -J
you just see the diff of added/removed tasks, not the diff of modifications to existing tasks).
Anyway, no worries if you can't get to this.. though it might be awhile until I or someone else has a chance to pick this up.
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Comment 10•4 years ago
|
||
bugherder |
Assignee | ||
Comment 11•4 years ago
|
||
Thanks for the write up and the patch! That helps a lot. Grabbing this and seeing what I can do (holding NI to remind me to keep at it).
Tried a first run with just the changes suggested in comment 8 at https://treeherder.mozilla.org/jobs?repo=try&revision=8c9392801f5938dc74935dc6fc1ab35e4c0a7769 -- that looks mostly okay. The failing tests look to be known intermittents.
I'll add some more configurations and see if anything breaks.
Assignee | ||
Comment 12•4 years ago
|
||
I think I misunderstood how this interacted with try initially, and thought I'd need to make modifications to get further flavours of the test to run on try, but this appears to not be true? Modifying the file above will just change what tests we're running on central and autoland?
Does it make sense following this that we'd end up with the same config here that we also arrived at for the fission tests in bug 1694828? That appears to be what I've arrived at. I'll push my patches shortly.
Assignee | ||
Comment 13•4 years ago
|
||
Assignee | ||
Comment 14•4 years ago
|
||
Depends on D110989
Assignee | ||
Comment 15•4 years ago
|
||
Depends on D110990
Assignee | ||
Comment 16•4 years ago
|
||
Depends on D110991
Comment 17•4 years ago
•
|
||
Yeah, it makes sense. The config changes themselves are pretty easy, it's the testing and triaging failures in try that is more time consuming. Though in this case sounds like you may be in the clear.
I also asked for help because there are a lot of these bugs to work through :). So thanks for picking this up!
Assignee | ||
Comment 18•4 years ago
|
||
Preparing to land. Try runs I've done look okay. I guess if these fail it'll be me as the traige owner who gets pinged anywho!
Comment 19•4 years ago
|
||
Comment 20•4 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/2399b20b93fe
https://hg.mozilla.org/mozilla-central/rev/1b35023795a1
https://hg.mozilla.org/mozilla-central/rev/030c9c64e42a
https://hg.mozilla.org/mozilla-central/rev/b3b783160873
Updated•4 years ago
|
Description
•