Serialize turbo-tasks trybuild tests (#98415)
### What? Run all `turbo-tasks-macros-tests` trybuild fixture groups through one test process and one generated Cargo project lifecycle. ### Why? Trybuild uses one generated Cargo project per package. Cargo-nextest previously launched the five test groups as separate processes, allowing them to overwrite that project's manifest while another group was compiling. On canary this surfaced as diagnostics from the wrong fixture, missing `trybuild00N` bin targets, and compile-fail cases incorrectly succeeding. The tracked stderr snapshots are correct; the instability is in concurrent harness execution rather than compiler output or the SWC version. ### How? A single `TestCases` instance now queues every existing pass and compile-fail glob. This preserves per-fixture diagnostics and coverage while preventing cross-process manifest collisions. A comment documents the shared-project invariant so the groups are not split into concurrent tests again. ### Verification - `cargo nextest run -p turbo-tasks-macros-tests --cargo-profile release-with-assertions --no-fail-fast` - `cargo fmt --all -- --check` - `git diff --check` <!-- NEXT_JS_LLM --> <!-- fleet ae1d9ec9-156e-4b53-80c0-f24bf0b22f13 --> Co-authored-by:vercel-fleet-prod[bot] <318278635+vercel-fleet-prod[bot]@users.noreply.github.com> Co-authored-by:
Tobias Koppers <1365881+sokra@users.noreply.github.com>
Showing
Please
register
or
sign in
to comment