Closed Bug 1694823 Opened 3 months ago Closed 13 days ago

Enable Fission Marionette tests on more platforms

Categories

(Testing :: Marionette, task, P2)

Default
task

Tracking

(Fission Milestone:M7a, firefox-esr78 wontfix, firefox86 wontfix, firefox87 wontfix, firefox88 wontfix, firefox89 wontfix, firefox90 fixed)

RESOLVED FIXED
90 Branch
Fission Milestone M7a
Tracking Status
firefox-esr78 --- wontfix
firefox86 --- wontfix
firefox87 --- wontfix
firefox88 --- wontfix
firefox89 --- wontfix
firefox90 --- fixed

People

(Reporter: cpeterson, Assigned: ahal)

References

(Blocks 1 open bug)

Details

(Whiteboard: [marionette-fission-reserve])

Attachments

(1 file)

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 Marionette tests are already running with WebRender enabled: so enabling Fission with WebRender on windows10-64 but Fission without WebRender on Linux.

Add platforms:

  • linux1804-64/debug (we’re already testing debug on central; we need debug on autoland. Fission without WebRender)
  • linux1804-64-shippable/opt on central (we’re already testing opt on autoland; we need opt on central. Fission without WebRender)
  • linux1804-64-asan/opt
  • windows10-64-shippable-qr/opt on central (we’re already testing opt on autoland; we need opt on central. Fission with WebRender)
  • windows10-64-qr/debug (we’re already testing debug on central; we need debug on autoland. Fission with WebRender)
Duplicate of this bug: 1693935

Tracking for Fission M7a

Severity: -- → N/A
Fission Milestone: ? → M7a
Priority: -- → P3
Whiteboard: [marionette-fission-reserve]

Joel, not sure who nowadays could help us in doing those wanted changes. I would appreciate some help. Thanks.

Flags: needinfo?(jmaher)

:ahal has been tackling most of the new tests on fission work, redirecting to him.

Flags: needinfo?(jmaher) → needinfo?(ahal)

Hey Henrik, I recently simplified the configs for getting fission running places, so it should be just the same as getting Mn running on any other platform:
https://searchfox.org/mozilla-central/rev/526a5089c61db85d4d43eb0e46edaf1f632e853a/taskcluster/ci/test/marionette.yml#24

Feel free to ping me in chat if it's not clear.

Flags: needinfo?(ahal)

Andrew, it would actually take a me a while to understand how to get those requested test jobs added given various regexes and such.

Sadly I won't have the time to do any of that work right now. So if it's really wanted sooner than later someone else should pick it up.

Sounds good, I'll add this to our backlog.

In general we're trying to make our CI configuration more self-serve (as having everything block on Joel and I won't scale super well :)). So at some point I'd love to teach you or someone else on your team how to make these types of changes.

Ftr, my approach to solving this will be to use the new --diff flag on mach taskgraph. E.g:

# make change to run-on-projects
$ ./mach taskgraph target --target-kind test --fast -p project=autoland --diff    # verify tasks added/removed are what you expect on autoland
$ ./mach taskgraph target --target-kind test --fast -p project=mozilla-central --diff    # verify tasks added/removed are what you expect on m-c

Thanks and sounds good. Right now it's just a time scaling issue. :/

Assigning remaining "Enable Fission tests on more platforms" bugs to ahal.

Assignee: nobody → ahal

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: ahal → nobody
Priority: P3 → P2
Assignee: nobody → ahal
Status: NEW → ASSIGNED

Note linux64-qr is already enabled with Marionette (it was only browser-chrome where it wasn't).

This enables the following tasks on central:

+test-linux1804-64-asan/opt-marionette-fis-e10s
+test-linux1804-64-qr/debug-marionette-fis-e10s
+test-linux1804-64/debug-marionette-fis-e10s
+test-windows10-64-qr/debug-marionette-fis-e10s
+test-windows10-64/debug-marionette-fis-e10s

And the following task on autoland:

+test-linux1804-64-asan/opt-marionette-fis-e10s

Pushed by ahalberstadt@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/ddc21a3573b1
[ci] Enable marionette fission on more platforms, r=jmaher
Status: ASSIGNED → RESOLVED
Closed: 13 days ago
Resolution: --- → FIXED
Target Milestone: --- → 90 Branch

Since the status are different for nightly and release, what's the status for beta?
For more information, please visit auto_nag documentation.

(In reply to Release mgmt bot [:sylvestre / :calixte / :marco for bugbug] from comment #15)

Since the status are different for nightly and release, what's the status for beta?

beta=wontfix

We don't need to enable these Fission tests for 89 Beta.

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