test(e2e): soak Web E2E ×10 (do not merge)#541
Closed
mokagio wants to merge 1 commit into
Closed
Conversation
Temporary throwaway pipeline stacked on the wp-env warm-up fix. Trims CI to the React build plus a single Web E2E step run 10× via `parallelism`, so one build yields 10 independent E2E runs against freshly provisioned wp-env instances. Confirms the maintenance-mode flakiness is gone across many samples, not just one. Not for merge. --- Generated with the help of Claude Code, https://claude.com/claude-code Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
github-actions
Bot
added
the
[Type] Automated Testing
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?
Throwaway soak test — do not merge. Stacked on #540. Trims CI to the React build plus a single Web E2E step run 10× via
parallelism, so one build produces 10 independent E2E runs, each against a freshly provisioned wp-env.Why?
#540 fixes an intermittent wp-env warm-up flake (WordPress maintenance mode corrupting the first editor REST call). A single green run doesn't prove an intermittent failure is gone. This uses Buildkite concurrency to sample the fixed E2E step many times in one build.
Success criterion
All 10
Test Web E2Ejobs pass. Then #540 can be marked ready, and this branch deleted.