test(turbopack): remove filesystem fuzzer unit tests (#99089)
### What? Remove the eight unit tests added to the manual filesystem-watcher fuzzer by #98982 and #98983. ### Why? This follows up on bgw's review feedback in [#98982](https://github.com/vercel/next.js/pull/98982#discussion_r4075847283) and [#98983](https://github.com/vercel/next.js/pull/98983#discussion_r4076126033) that unit tests are overkill for this stress-testing CLI. Its supported behavior is exercised by running the fuzzer itself. ### How? Remove only the fuzzer's `#[cfg(test)]` module. Both production fixes from the original PRs remain unchanged. Verified with: - `cargo fmt -- --check` - `cargo check -p turbo-tasks-fuzz` - `cargo clippy -p turbo-tasks-fuzz --all-targets -- -D warnings -A deprecated` - `cargo build --release -p turbo-tasks-fuzz` - 30-second manual smoke runs for normal reads, tracked read/writes, and directory symlinks (443 total iterations; no panics or terminal errors) <!-- NEXT_JS_LLM --> <!-- fleet 6488265d-2685-49d3-b632-6511b4b47690 --> 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> Co-authored-by:
Benjamin Woodruff <180404+bgw@users.noreply.github.com>
Showing
Please
register
or
sign in
to comment