[Fix] Prevent concurrent tests from reusing environment names - #3077
Merged
Merged
Conversation
Contributor
roomote-roomote
Bot
requested review from
brunobergher,
daniel-lxs and
mrubens
as code owners
September 21, 2026 22:47
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.
What changed
Default environment factory names now retain their readable lorem stem and append a UUID. Explicitly provided names remain unchanged, and focused regression coverage verifies both behaviors.
Why this change was made
Concurrent Vitest workers can generate the same two-word lorem name, causing PostgreSQL
23505failures on the globally uniqueenvironments.nameindex during unrelated test setup.Impact
Database-backed tests no longer depend on a collision-prone random-word default. Production environment naming and caller-provided fixture names are unchanged.