Open Bug 1585344 Opened 1 year ago Updated 1 month ago

[meta] Get Talos responsiveness tests working with Fission enabled

Categories

(Testing :: Talos, task, P3)

Version 3
task

Tracking

(Fission Milestone:M7)

Fission Milestone M7

People

(Reporter: mconley, Unassigned)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

(Keywords: meta, Whiteboard: fission-tests)

The front-end desktop perf team would like to:

  1. Check to see if the Talos tests that measure browser responsiveness (as opposed to page load, graphics, or video performance) work with the Fission autostart pref enabled, and fix them if they're not.

  2. Ensure that the Talos tests are exercising paths that are realistically going to be hit when Fission is enabled by default.

  3. Get a Fission-enabled Talos variant running in CI so we can start collecting measurements and catching regressions.

Depends on: 1585427
Depends on: 1586767
Depends on: 1583914
Depends on: damp-fission-meta
Depends on: 1586938
Priority: -- → P1

Enabling Talos is a prerequisite for enabling Fission in Nightly (M6).

Fission Milestone: --- → M6

Tentatively moving P1 Fission M6 bugs to M6a.

Fission Milestone: M6 → M6a

Adjusting priority based on the priority of the remaining open dependencies.

Priority: P1 → P3
Whiteboard: fission-tests
Fission Milestone: M6a → M6b
Fission Milestone: M6b → M6c

Dave - where does this stand? Any eta? We're moving this to m6c to not block fission in nightly, but it would be nice to monitor this

Flags: needinfo?(dave.hunt)

(In reply to Randell Jesup [:jesup] (needinfo me) from comment #5)

Dave - where does this stand? Any eta? We're moving this to m6c to not block fission in nightly, but it would be nice to monitor this

The only open dependency is bug 1454025, which is a DAMP meta bug with additional open dependencies. My team don't maintain the DAMP tests, so I can't comment on the status of those.

Flags: needinfo?(dave.hunt)

Blocked on DAMP (bug 1454025) which is tracked for M7.

Fission Milestone: M6c → M7

Based on the description in the summary, I think it makes more sense to block this bug on Bug 1673308 (fix DAMP with fission) rather than on Bug 1454025 (add more coverage for fission).

We already hit all the relevant codepaths with our current DAMP test suite, but we don't have tests with many iframes + devtools, which is the intent behind Bug 1454025. I think fixing the devtools DAMP test suite to fully work with Fission enabled should be sufficient here.

Depends on: 1673308
No longer depends on: damp-fission-meta
You need to log in before you can comment on or make changes to this bug.