Ignore flaky turbo-tasks-fs watcher tests in CI (#100627)
### What? Ignores four timing-sensitive `turbo-tasks-fs` watcher tests in GitHub Actions while keeping them enabled for local runs: - `irrelevant_events_do_not_delay_invalidation` - `repeated_writes_to_tracked_file_are_debounced` - `recreated_directory_is_watched_again` - `read_registered_before_watch_is_restored_is_invalidated` ### Why? These watcher tests depend on filesystem-event and debounce timing, which is unreliable on CI runners and causes flaky failures. ### How? - `turbo-tasks-fs` gets an opt-in `ci` cargo feature. Each of the four tests is ignored only when that feature is enabled. The attribute is placed after the rstest cases so it applies to every generated case (14 in total). - A dedicated `test-cargo-unit-ci` script and Turbo task enable `turbo-tasks-fs/ci` for the nextest and doctest commands. A separate script is needed because extra Turbo args are appended only to the final command in the existing `&&` chain. - The `test-cargo-unit` GitHub Actions job now runs `test-cargo-unit-ci`. The existing local `test-cargo-unit` command is unchanged and still runs these tests. ### Verification - `cargo test -p turbo-tasks-fs --lib --features turbo-tasks-fs/ci -- watcher::tests`: 6 passed, 14 ignored - `cargo test -p turbo-tasks-fs --lib -- watcher::tests`: 20 passed, 0 ignored - Compared `cargo nextest list` JSON output with and without the feature: exactly the 14 targeted cases change ignore status. - Turbo dry run resolves `@next/swc#test-cargo-unit-ci` to the feature-enabled commands. <!-- NEXT_JS_LLM --> <!-- fleet 3dc2faec-b6b1-43eb-ae2d-4951789fb457 --> 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