fix: coaching test temp-dir race under nextest (Windows CI flake) - #405
Merged
Conversation
…in-process temp_dir_for_test()'s uniqueness came from an in-process atomic counter, but nextest runs each test in its own process -- every process's counter starts back at 0, so every test using this helper collided on the exact same temp path. Windows' stricter file locking turns that race into a hard failure (parse_old_file_without_enforce_line_defaults_to_false failing intermittently in CI); Unix mostly tolerates it silently. Mixes in the pid so concurrent test processes never share a path.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe test temporary-directory helper now includes the process ID and an atomic counter in generated paths. This prevents collisions across concurrent processes and preserves uniqueness within each process. ChangesTest directory isolation
Estimated code review effort: 1 (Trivial) | ~5 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Found while chasing an unrelated Windows CI failure on another PR:
coaching::rule::tests::parse_old_file_without_enforce_line_defaults_to_falsefails intermittently onwindows-latest.Root cause:
temp_dir_for_test()'s uniqueness came from an in-processstatic AtomicU64counter. nextest (adopted in #399) runs each test in its own process, so every process's counter starts back at 0 — every test in this module that calls the helper resolves to the exact same temp directory path. Windows' stricter file locking turns that race into a hard failure; Unix mostly tolerates it silently, which is why this only ever surfaced onwindows-latest.Fix: mix
std::process::id()into the path so concurrent test processes never collide. Counter stays, still covers multiple calls within one process.Test plan
cargo test -p agentflare coaching::rule::— 21 passedcargo fmt --checkcleanSummary by CodeRabbit