fix(test/win): platform-specific cold-start target (router)#49
Merged
masonwyatt23 merged 1 commit intomainfrom Apr 29, 2026
Merged
fix(test/win): platform-specific cold-start target (router)#49masonwyatt23 merged 1 commit intomainfrom
masonwyatt23 merged 1 commit intomainfrom
Conversation
Hosted Windows runners are virtualized + antivirus-scanned, so bun child spawn cold-start can take well over 1s without any actual code regression in the router. Tightens POSIX bound (still 300ms) and uses a separate 1500ms bound on Windows that still catches genuine regressions (a regressed router takes ~3-4s per run there). Local POSIX: median 71.9ms over 3 samples (well under 300ms). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
1 participant
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.
Why
The
router · cold-start latencytest asserts median<300ms over 3 samples to catch perf regressions in the router. POSIX hosts comfortably hit ~70-100ms.Hosted Windows runners are virtualized + antivirus-scanned, so bun child spawn cold-start can take well over 1s without any code change in the router. This causes intermittent flakes on Windows CI (saw 953ms median in PR #27's last run).
What
Splits the assertion target by platform:
Stats
🤖 Generated with Claude Code