Closed Bug 1585592 Opened 5 years ago Closed 3 years ago

[meta] Enable Fission for Talos

Categories

(Testing :: Talos, task, P1)

Version 3
task

Tracking

(Fission Milestone:Future)

RESOLVED FIXED
Fission Milestone Future

People

(Reporter: davehunt, Unassigned)

References

(Depends on 1 open bug)

Details

(Keywords: meta, Whiteboard: fission-perf, fission-soft-blocker, fission-meta)

This is a tracking bug for getting the Talos tests in CI with Fission enabled.

Type: enhancement → task
Depends on: 1585344
Blocks: 1594631

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

Fission Milestone: --- → M6
No longer blocks: 1582756

Tentatively moving P1 Fission M6 bugs to M6a.

Fission Milestone: M6 → M6a
Whiteboard: fission-tests

We are running all Talos tests on linux64-qr and win64-qr as tier 2.

Can we enable Fission Talos on macOS as tier 2 now, too?

Fission Milestone: M6a → M6b
Depends on: 1638934

(In reply to Chris Peterson [:cpeterson] from comment #3)

We are running all Talos tests on linux64-qr and win64-qr as tier 2.

Can we enable Fission Talos on macOS as tier 2 now, too?

I've opened bug 1638934.

Fission Milestone: M6b → M6c

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

Fission Milestone: M6c → M7
Whiteboard: fission-tests → fission-tests, fission-perf

One of the dependencies is tracking M8 so moving this meta to M8.

Fission Milestone: M7 → M8

Moving this meta bug from Fission M8 to MVP because all of the blocking bugs are blockers for either Fission MVP or Future.

Fission Milestone: M8 → MVP

This bug is a soft blocker for Fission MVP. We'd like to fix it before our Release channel rollout, but we won't delay the rollout waiting for it.

Whiteboard: fission-tests, fission-perf → fission-perf, fission-soft-blocker
Fission Milestone: MVP → Future
Whiteboard: fission-perf, fission-soft-blocker → fission-perf, fission-soft-blocker, fission-meta

Despite the remaining blocker, Talos tests are running under Fission.

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