fix: add --no-lock
to spawned process args in tests
#4168
Merged
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.
I noticed that tests containing spawned processes that use the Deno binary tend to be flaky. There have been a few instances in the past that these processes fail because the runtime is unable to parse the contents of the lockfile. I.e. race condition.
This fix adds the
--no-lock
CLI flag to all such instances. Hopefully, we'll see a noticable reduction in test flakiness in CI.