[Tests] Fix another early termination in tests #1812
Merged
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
cachemeifyoucan
force-pushed
the
fix-early-termination
branch
from
bfcb5d9 to
0fa5ae1
Compare
When running swift-driver test suite with an older compiler that doesn't support bridging header chaining, the second part of the bridging header caching test will just be a single job, from which the default executor will run the swift-frontend in-place. This will cause the test suite to early exit regardless of the state of the test suite.
cachemeifyoucan
force-pushed
the
fix-early-termination
branch
from
0fa5ae1 to
e9212a4
Compare
|
@swift-ci please test |
|
ping |
nkcsgexi
approved these changes
Feb 19, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When running swift-driver test suite with an older compiler that doesn't support bridging header chaining, the second part of the bridging header caching test will just be a single job, from which the default executor will run the swift-frontend in-place. This will cause the test suite to early exit regardless of the state of the test suite.