Test/prep for multiple swift versions #44
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
loonatick-src force-pushed the test/prep-for-multiple-swift-versions branch 2 times, most recently from ada1b19 to b4e99be Compare loonatick-src force-pushed the test/prep-for-multiple-swift-versions branch 2 times, most recently from 2f57cab to 33bdda4 Compare loonatick-src force-pushed the test/prep-for-multiple-swift-versions branch from 1cc2aa9 to 33bdda4 Compare added 10 commits May 2, 2025 14:32
loonatick-src force-pushed the test/prep-for-multiple-swift-versions branch from 33bdda4 to ec5a9c8 Compare 
JaapWijnen approved these changes May 2, 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.
This PR adds support for multiple Swift versions and separates the tests for macOS vs Linux.
check.pyscript itself selects the appropriate Swift version -- if e.g. 6.1 ground truth is not present, then it will select the next lower version, i.e. 6.0.3 as of this PR. This handles the default case where the crasher's status has not changed.containerkey. Conditionally settingcontainertonulldoes not work.# OKground truth must be present, i.e. there is now one way to specify OK ground truths. Before this, no compiler output + no ground truth file implied OK as well.