fix(ci): bring Windows test matrix under five minutes - #267
Merged
Merged
Conversation
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
EBUSYcase.Related to #262. This PR does not automatically close the issue.
Evidence at
c54f6189Both the workflow-dispatch run and the PR-triggered run passed all 13 jobs. Windows test-job elapsed times, measured from job start to completion:
The Ubuntu/Node 24 coverage gate reported 94.31% lines, 83.17% branches, and 93.44% functions. Locally, the 36 merge tests fell from 6.4 seconds to 0.63 seconds on macOS/Node 26.
Local checks passed: full
pnpm testwith coverage and withAK_TEST_COVERAGE=0under the strict real-state tripwire; focused merge and runner tests; UI tests; typecheck; lint and Markdown lint; build check; dispatch-surface tests; andactionlint.Remaining verification
These are two completed runs at the exact PR head. Issue #262 calls for ten consecutive runs to establish the median and variation. Keep that stability check visible before treating the issue as closed or the branch as merge-ready.