Closed Bug 1694836 Opened 4 years ago Closed 3 years ago

Enable Fission mochitest-remote tests on more platforms

Categories

(Firefox Build System :: Task Configuration, task, P3)

task

Tracking

(Fission Milestone:Future, firefox-esr78 wontfix, firefox86 wontfix, firefox87 wontfix)

RESOLVED INCOMPLETE
Fission Milestone Future
Tracking Status
firefox-esr78 --- wontfix
firefox86 --- wontfix
firefox87 --- wontfix

People

(Reporter: cpeterson, Unassigned)

References

(Blocks 1 open bug)

Details

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”) for tests already running with WebRender enabled: so enabling Fission with WebRender on linux1804-64-qr but Fission without WebRender on linux1804-64-asan and Windows.

Add platforms:

  • linux1804-64-qr/debug
  • linux1804-64-qr/opt on autoland, shippable/opt on central
  • linux1804-64-asan/opt
  • windows10-64/debug
  • windows10-64/opt on autoland, shippable/opt on central
Component: DOM: Content Processes → Mochitest
Product: Core → Testing

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

Assignee: nobody → ahal
Depends on: 1601245
Component: Mochitest → Task Configuration
Product: Testing → Firefox Build System

According to :whimboo remote agent does not support Fission and these tests would all fail. So unassigning for now.

Assignee: ahal → nobody

TBD. If running mochitest-remote tests with Fission doesn't block Fission (bug 1601245), then we can defer this bug to Fission Future. I am waiting to hear from :whimboo in bug 1601245.

Chris, is this accurate for M8? There is no triage owner and no one seems to be looking into this.

Flags: needinfo?(cpeterson)

I don't think we require mochitest-remote on all platfoms for Fission M8, or even MVP.

(In reply to Neha Kochar [:neha] from comment #6)

I don't think we require mochitest-remote on all platfoms for Fission M8, or even MVP.

We are not currently running mochitest-remote tests with Fission on any platform. I think we should run every test on at least one platform before experimenting on Release.

(In reply to Neha Kochar [:neha] from comment #5)

Chris, is this accurate for M8? There is no triage owner and no one seems to be looking into this.

These "Enable Fission tests on more platforms" bugs are on Andrew Halberstadt's radar, so I'll assign them all to him.

Assignee: nobody → ahal
Flags: needinfo?(cpeterson)

According to https://bugzilla.mozilla.org/show_bug.cgi?id=1601245#c8 the remote agent (on which these tests depend) is not fission compatible (and there's apparently even question as to whether they want it to be compatible). So this appears to be blocked until that's resolved.

Assignee: ahal → nobody
Flags: needinfo?(cpeterson)

(In reply to Andrew Halberstadt [:ahal] from comment #9)

According to https://bugzilla.mozilla.org/show_bug.cgi?id=1601245#c8 the remote agent (on which these tests depend) is not fission compatible (and there's apparently even question as to whether they want it to be compatible). So this appears to be blocked until that's resolved.

I still don't fully understand the difference between bug 1601245 and this bug. They sound like duplicates to me, but keeping this bug open is not a big deal.

For now, since bug 1601245 has Fission Milestone "Future" (not a blocker for Fission MVP), then I will defer this bug to Fission Milestone "Future".

Fission Milestone: M8 → Future
Flags: needinfo?(cpeterson)

Closing this bug as unnecessary because this future test work will be fixed when we enable Fission by default in Nightly 96 and switch all tests from e10s to Fission.

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.