fix: serialize concurrent artifact writers - #41
Merged
Merged
Conversation
Lock each artifacts directory for the full Testfold run so independent processes cannot delete or parse one another's suite files. Load TypeScript configs through the published tsx runtime and release v0.4.3.
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.
Fixes cross-process artifact cleanup/write races by holding an ownership-safe artifacts-directory lock for the full run. Also restores advertised TypeScript config loading in the published CLI by moving tsx to runtime dependencies.\n\nVerified under Node 24.20.0: npm run verify (341 unit, 2 integration), plus three concurrent Testfold processes returned distinct 5/27/34-test results without ENOENT or result mixing.