test: tolerate Windows timing jitter - #736
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
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)
WalkthroughThis PR adjusts timing-budget tolerance in a performance test to improve reliability across platforms. The assertion now applies platform-dependent jitter allowance—5ms on Windows, 1ms elsewhere—instead of a uniform 1ms tolerance, reducing intermittent test failures on slower or variable-latency platforms. ChangesTest Timing-Budget Assertion
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Suggested labels
Suggested reviewers
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
📊 Coverage ReportCoverage report not available
Generated by PR Automation (Story 6.1) |
Summary
Validation
Context
Follow-up to the Windows Node 18 CI failure after PR #735. The failed assertion was a millisecond-level timing flake: expected less than or equal to 2ms, received 3ms. It is not related to the Pro installer hotfix.
Summary by CodeRabbit