[6.4] Tests: Update withKnownIssue conditional#10048
Merged
bkhouri merged 1 commit intoMay 12, 2026
Merged
Conversation
Contributor
Author
|
@swift-ci test |
A Windows tests fails with Swift 6.2, but is fixed with Swift 6.3. Update the withKnownIssue when bloc to reflect this
bkhouri
force-pushed
the
t/6.4.x/remove_known_issue_with_windows_tests
branch
from
d405aae to
75943cb
Compare
Contributor
Author
|
@swift-ci test |
bkhouri
changed the title
bkhouri
changed the title
Contributor
Author
|
@swift-ci test windows |
Contributor
Author
|
@swift-ci test self hosted windows |
bkhouri
requested review from
bripeticca,
cmcgee1024,
daveinglis,
daveyc123,
dschaefer2,
jakepetroules,
owenv,
plemarquand and
rconnell9
as code owners
rconnell9
approved these changes
May 12, 2026
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.
A Windows tests fails with Swift 6.2, but is fixed with Swift 6.3. Update the withKnownIssue when bloc to reflect this