fix(e2e): dedupe automine test cmds causing mass container-kill flakes#24547
Merged
Conversation
vezenovm
added
ci-full
vezenovm
changed the title
The tests array listed the automine subdirectories explicitly and also kept the src/automine/!(simulation)/**/*.test.ts catch-all (a merge artifact), so every nested automine test was emitted as two identical cmds. Both copies run under the same docker container name; when they overlap, one docker_isolate force-removes the other's live container, failing that test, and the fresh-named retry then passes. That is the mass automine FLAKED pattern (49 per run) on this stack. The deduplicated unique cmd set is unchanged (145 automine jobs).
vezenovm
force-pushed
the
mv/fix-automine-flakes
branch
from
July 6, 2026 17:10
458e0dc to
a7e6a40
Compare
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.
Stacked on #24477. Fixes the 49-per-run automine FLAKEs reported there and on this PR's first run.
Root cause (
yarn-project/end-to-end/bootstrap.sh): thetestsarray listed the automine subdirectories explicitly and also kept thesrc/automine/!(simulation)/**/*.test.tscatch-all (a merge artifact from merging merge-train/fairies-v5 into mv/e2e-onchain-delivery-harness), so every nested automine test was emitted as two byte-identical cmds (268 jobs for 145 tests). Both copies run under the same docker container name. When the two copies overlap in time, the later one's docker_isolate force-removes the earlier one's live container (or wins the name-conflict retry added in #24477), the earlier test fails, and its automatic retry (which gets a freshNAME_POSTFIX) passes: a deterministic FLAKED-with-code-0 for every overlapping pair, which is why the count sits near 49 on every run and why onlysrc/automine/**flakes. When the copies do not overlap, the second is skipped by the test cache, hiding the duplication. The parent branch's "docker container name conflicts" were the same duplication seen from the other side.