Make test suites run sequentially with respect to other test suites#200
Merged
katiewasnothere merged 1 commit intoapple:mainfrom Jun 16, 2025
Merged
Conversation
Signed-off-by: Kathryn Baldauf <k_baldauf@apple.com>
katiewasnothere
force-pushed
the
seq_test_suites
branch
from
bb3b479 to
24e5dcc
Compare
adityaramani
approved these changes
Jun 16, 2025
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.
Right now swift testing does not have finer grain test parallelization controls. As a result our easy options are either to have ALL tests in ALL test suites run sequentially or have tests within a given test suite run sequentially while other test suites are run at the same time.
This has been problematic for our CI since we opted for the second option above, where, for examples, the tests in the builder test suite run sequentially, but the builder test suite runs at the same time as the container run test suite. When this happens, a lot of different tests try to pull the necessary images for testing at the same time, causing some tests to timeout.