[Do not merge] Reduced test case for strange test crashes #630
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
This is a very odd bug that is showing up in CI and on the command line, but not in Xcode with a similar toolchain selected. The `GoodBadFunctionTests.swift` file has a reduced test case that demonstrates the problem: With this code included, I see several _other_ tests that crash, even in different test modules. The problem disappears if you comment out the call to `badFunction`, but then re-appears if you make `badFunction` internal instead of fileprivate. I've been testing this with `swift-DEVELOPMENT-SNAPSHOT-2023-01-30-a.xctoolchain`.
|
@swift-ci Please test |
|
@swift-ci test Windows |
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 is a very odd bug that is showing up in CI and on the command line, but not in Xcode with a similar toolchain selected. The
GoodBadFunctionTests.swiftfile has a reduced test case that demonstrates the problem: With this code included, I see several other tests that crash, even in different test modules.The problem disappears if you comment out the call to
badFunction, but then re-appears if you makebadFunctioninternal instead of fileprivate. I've been testing this withswift-DEVELOPMENT-SNAPSHOT-2023-01-30-a.xctoolchain.