test: limit test-default ITs to 4 in parallel - #25422
Draft
mcollovati wants to merge 3 commits into
Draft
Conversation
Contributor
Member
|
Is it a parallel limit that is needed or a generic wait for the app to fully start before starting ITs? |
Collaborator
Author
|
Wait before starting tests might work. But anyway running 50 parallel browsers seems a bit too much to me |
Without a cap TestBench starts all of them at once, and the browser burst floods the dev server while it is still installing packages and pre-bundling frontend dependencies.
Deriving groups from ${excludedGroups} resolved to the empty value the
same profile sets, leaving no filter at all, so the category list now
lives in its own property that the profile can reference.
mcollovati
force-pushed
the
test/ci-flaky-tests
branch
from
September 3, 2026 05:24
e699dcf to
b0bc72a
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
2 participants
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.
Without a cap TestBench starts all of them at once, and the browser burst floods the dev server while it is still installing packages and pre-bundling frontend dependencies.