[6.2] Build foundation tests in release #84445
Open
+12
−4
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
…Windows We currently rebuild swift-syntax, swift-foundation-icu and swift-foundation twice: Once to test swift-foundation and once to test swift-corelibs-foundation. Using a unified build for both projects means that we only need to rebuild them once, saving ~5 minutes. (cherry picked from commit 61f833c) (cherry picked from commit 7ce649c)
|
@swift-ci please test |
owenv
approved these changes
Sep 22, 2025
This was referenced Sep 23, 2025
hborla
approved these changes
Sep 23, 2025
|
@swift-ci please test Windows platform |
1 similar comment
|
@swift-ci please test Windows platform |
|
@swift-ci please test Windows |
compnerd
approved these changes
Oct 9, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 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.
-j 1change in build.ps1 for foundation tests #83606). We have a swift-driver (Use UUID for response file names and add 'resolveArgumentList' API which contains original command-line if a response file is used swift-driver#1989) and swift-build (Adopt uniquely-named driver response files swift-build#809) change up for this, but this keeps blocking release/6.2 PRs until that's in.-j 1change in build.ps1 for foundation tests #83606 is the underlying issue