test(turbopack): add polling to filesystem watcher fuzzer (#98863)
### What? Adds an opt-in polling mode to the manual `turbo-tasks-fuzz fs-watcher` stress harness through `--poll-interval-ms`. Stack: **3/5** · Previous: #98983 · Next: #98737 ### Why? The fuzzer previously exercised only native filesystem events. A configurable polling mode enables sustained stress testing of PollWatcher invalidation behavior and provides a direct before/after control for the notify upgrade in the next stack layer. ### How? A positive, nonzero interval is mapped to `DiskWatcherConfig.poll_interval`; omitting it preserves the native-watcher defaults. The fuzzer passes an empty `DiskFileSystemMap`, matching the default `DiskFileSystem::new` behavior while using the extended constructor needed for watcher configuration. Manual runs cover ordinary reads, tracked read-derived writes, recursive/nonrecursive modes, directory recreation, and native omission. CLI help also documents that notify's PollWatcher retains whole-second mtime precision for non-files, so multiple symlink changes within one second can be missed; this upstream limitation is reported rather than hidden with timing workarounds. <!-- 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