Repository navigation
test: handle transient busy fixture removal on Windows - #22
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
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.
The Windows/Node 24 main run passed the development-child termination assertions but failed while removing the disposable fixture with
EBUSY. Give that final directory removal the same bounded retry policy already used by the process-backend fixture.The tests still require owned children to exit and unlink the SDK junction before cleanup. Only test cleanup changes; published package files are identical to the 0.11 candidate already checked against released 0.3.2–0.10.0 archives.
Validation: all seven local development-tools tests pass. Full Windows/Linux × Node 22/24 CI remains required before releasing 0.11.