test(turbopack): remove remaining test unmarks (#98376)
### What? Remove all 14 remaining non-API `unmark_top_level_task_may_leak_eventually_consistent_state()` calls from Turbopack tests across eight files. The manual mark/unmark consistency test remains unchanged because it intentionally covers this API. ### Why? Top-level test reads should state their consistency boundary explicitly instead of globally permitting eventually consistent state. Removing the suppressions makes accidental eventual reads fail normally and keeps each test aligned with production consistency rules. ### How? Use coarse operation roots for collectible and recomputation scenarios where the operation can settle, and narrower phase boundaries for tests that mutate dependencies. Preserve graph-sensitive behavior by extracting task IDs without resolving in parent-count tests and by strongly reading the existing leaf root without inserting wrapper parents in GC tests. Error tests use separate operation and plain-future helpers so their expected context stacks remain unchanged. ### Verification - `cargo fmt --all -- --check` - `timeout 300 cargo test -p turbo-tasks-backend --test parent_count --test trait_ref_cell_mode --test recompute_collectibles --test recompute --test collectibles --test errors --test immutable --test gc_collection` (36 passed) - `git diff --check` <!-- NEXT_JS_LLM --> <!-- fleet 475180cd-06a7-4669-89b5-a2029a3a18c9 --> Co-authored-by:vercel-fleet-prod[bot] <318278635+vercel-fleet-prod[bot]@users.noreply.github.com> Co-authored-by:
Luke Sandberg <210140+lukesandberg@users.noreply.github.com>
Showing
Please
register
or
sign in
to comment