Open Bug 1693640 Opened 3 months ago Updated 3 months ago

Run devtools fission tests on opt builds on autoland (instead of shippable)


(DevTools :: General, task, P3)



(Fission Milestone:M8)

Fission Milestone M8


(Reporter: jdescottes, Assigned: jdescottes)


(Blocks 1 open bug)



(1 file, 1 obsolete file)

We initially decided to run devtools fission mochitests on shippable for autoland when we moved them to tier1, so that we would align with the platforms already used on central.

But shippable builds are more expensive, and we should be able to switch to regular opt builds for autoland.

The jobs for devtools fission on linux opt non shippable don't exist for now.
So it's not just a matter of updating the platforms.

Hi Joel,

I see we can't schedule Mochitest Fission jobs on Linux 64 opt platforms, they seem available on shippable builds.
I can't find them either using try fuzzy or using "add new jobs" on treeherder.
I don't know where this is defined though and if it's something we can change?

Example: the job opt-mochitest-devtools-chrome-fis-e10s-1 is not available under test-linux1804-64, only under test-linux1804-64-shippable.


Flags: needinfo?(jmaher)
Fission Milestone: --- → M7

I don't want to leave the needinfo hanging so long, but unfortunately I don't know how to solve this- I did spent a few hours looking into this and see that this is a problem (also with browser-chrome). My hacking didn't seem to help, so I need to spend more time on this...ideally in the next week I have traction here.

See Also: → 1694825

I have filed bug 1695083, this should allow things to work normally- I have more testing to do, maybe my initial findings are not going to work out- but I am a lot closer and will continue to find a solution there.

Depends on: 1695083
Flags: needinfo?(jmaher)

Thanks for taking a look at this Joel! Really appreciated, I had no idea how to make progress here.

Moving from Fission M7 (Beta experiment) to M8 (Release experiment) because switching the DevTools test config on autoland doesn't need to block our Beta experiment.

Fission Milestone: M7 → M8
Summary: Run devtools fission tests on opt builds on trunk (instead of shippable) → Run devtools fission tests on opt builds on autoland (instead of shippable)

All the other browsertime tasks ignore non-shippable platforms except for this
one. It was causing problems for a later patch in this stack.

Comment on attachment 9206729 [details]
Bug 1693640 - [ci] Ensure browsertime tp6 ignores non-shippable fission platforms, r?#perftest-reviewers

Revision D107107 was moved to bug 1695083. Setting attachment 9206729 [details] to obsolete.

Attachment #9206729 - Attachment is obsolete: true

Once the patches in bug 1695083 land, then opt-mochitest-devtools-chrome-fis will start showing up in ./mach try fuzzy --full. To get them there without --full, they need to be running on central/autoland. Now setting the fission-run-on-projects key here should work.

:jdescottes, now that bug 1695083 is landed (just now on autoland), your changes should be a lot easier to make.

You need to log in before you can comment on or make changes to this bug.