[v8] Optimize integration test execution to reduce infrastructure load related flakes #3681
Conversation
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
anujc25
changed the title
Samze
approved these changes
Jan 14, 2026
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.
Description of the Change
This PR optimizes the integration test execution in CI to reduce infrastructure load and improve test reliability.
The main change splits the
integration-tests-full-ciMakefile target into 3 sequential batches instead of running all 6 test suites together with high parallelism. Additionally, the number of parallel nodes is reduced from 12 to 4 in the GitHub Actions workflow.Test suites are now grouped logically into batches that run sequentially with controlled parallelism to prevent infrastructure overload while maintaining reasonable test execution time.
Why Is This PR Valuable?
This change addresses infrastructure load issues that cause test failures due to resource contention. By reducing concurrent load from 12 parallel nodes to 4 and spreading test execution over time through batching, the tests become significantly more stable and reliable on resource-constrained infrastructure.
Users running integration tests in CI environments with limited resources will benefit from more consistent test results and fewer infrastructure-related failures.
Applicable Issues
List any applicable GitHub Issues here
How Urgent Is The Change?
This change improves the reliability of integration tests in CI but is not time-sensitive.