Use case
ACTOR_TS_SKIP_FLAKY_MNS=1 is set in all three workflows that run the unit suite (test.yml, multi-runtime.yml, publish.yml), which describe.skips three suites: tests/multi-node/lease-majority.test.ts, tests/multi-node/parallel-pubsub.test.ts, tests/unit/testkit/ParallelMultiNodeSpec.test.ts. There is no scheduled job that re-attempts them — they are permanently dark in CI, so a regression in these paths is invisible until someone runs the full suite locally. (bunfig.toml additionally strips them from the coverage denominator, hiding the quarantine twice.)
Proposed approach
- A nightly workflow that runs exactly these three suites without the skip env,
continue-on-error, with log capture — same pattern as the existing nightly integration jobs.
- On repeated green runs, evaluate un-quarantining (the documented root cause is Bun-on-hosted-runner worker respawning, which may have been fixed by newer Bun releases).
- Surface breach/regression as a workflow-summary annotation rather than a red PR check.
Acceptance criteria
Related
Use case
ACTOR_TS_SKIP_FLAKY_MNS=1is set in all three workflows that run the unit suite (test.yml,multi-runtime.yml,publish.yml), whichdescribe.skips three suites:tests/multi-node/lease-majority.test.ts,tests/multi-node/parallel-pubsub.test.ts,tests/unit/testkit/ParallelMultiNodeSpec.test.ts. There is no scheduled job that re-attempts them — they are permanently dark in CI, so a regression in these paths is invisible until someone runs the full suite locally. (bunfig.tomladditionally strips them from the coverage denominator, hiding the quarantine twice.)Proposed approach
continue-on-error, with log capture — same pattern as the existing nightly integration jobs.Acceptance criteria
Related