CI: Don't xcbeautify Swift Testing suites
#3425
Merged
Conversation
This file contains 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
stephencelis
changed the title
xcbeautify Swift Testing suites
Test expected failure is flakey, so hopefully will pass more consistently now.
mbrandonw
approved these changes
Oct 7, 2024
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.
This PR originally introduced CI for our new benchmark suite, but without a dedicated runner the results are too variable to measure regressions accurately. While preparing, I noticed that test failures on our new Swift Testing suites weren't surfacing information about the expectation failures due to lack of xcbeautify support: cpisciotta/xcbeautify#313
We can bring back xcbeautify for these suites whenever support lands.