Periodic merge main -> release 6.2 #404
Open
+2,450
−1,981
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 moves some Windows and macOS specific code out of core.
…s in test targets which exclusively use Swift Testing and enable LD_WARN_UNUSED_DYLIBS (#379) Fixes rdar://148694760
…the developer path (#381)
…fferent toolchain (#385)
Eliminate the package dependency on swift-crypto to simplify the bootstrapped build. Instead, vendor the SHA256 implementation from swift-tools-support-core and use it as a fallback if neither WinSDK nor CryptoKit is available.
This should hopefully give us more insight into flaky tests.
…requests Noticed this; fix it before it bites someone later...
Make them work on Linux, and standardize how they're skipped if SDKs are not installed. rdar://148676808
Send that to /dev/null instead
This removes support for compiling files with bitcode from SWBuild, as this functionality is no longer supported. This removes a lot of functionally dead code. Support for stripping bitcode from copied files remains, as there are extant libraries and XCFrameworks which contain bitcode, which must be stripped. Bitcode was only supported for a subset of platforms, to the assignment of STRIP_BITCODE_FROM_COPIED_FILES in Settings based on platform remains, so time isn't spent stripping nonexistent bitcode from other platforms. Some interfaces which Xcode uses continue to refer to bitcode for compatibility, but effectively do nothing. Note that the references to bitcode in the OpenCL support are a concept internal to that tool, and independent of the support being removed here. rdar://148287993
…uild description cache in tests If we've told the build description manager to never evict build descriptions from its cache, ensure that the cache isn't attached to the heavy cache global state, so that it isn't cleared by other tests running concurrently.
Explicit module arguments are removed for the arguments returned for indexing. Also disable them for preparation in general so we're not mixing between the two. Resolves rdar://147354913.
owenv
requested review from
jonathanpenn,
jakepetroules,
mirza-garibovic,
mhrawdon and
neonichu
as code owners
|
@swift-ci test |
Use our FSProxy abstraction instead of Foundation, which doesn't suffer from swiftlang/swift-foundation#860
jakepetroules
approved these changes
Apr 12, 2025
neonichu
approved these changes
Apr 14, 2025
…nings. (#405) These warnings are nudging developers to adopt features before they become required. They're not just recommendations. Resolves rdar://149086651.
Add the `freebsd` platform to the new PIF encoding API (i.e., `ProjectModel`). We need this when sending over the PIF JSON from SwiftPM (with the new `--build-system swiftbuild` option) given SwiftPM `PackageModel.Platform` already supports FreeBSD.
…ntUser`. (#411) `FileManager.homeDirectoryForCurrentUser` is only available for macOS on Apple platforms, which breaks building SwiftBuild for iOS.
|
@swift-ci test linux |
…ith target location (rdar://149397709)
rdar://149248232
jakepetroules
approved these changes
Apr 16, 2025
…ithGeneratedEntryPoint
…to combine all hits/misses Separating by compiler is not that useful, this is intended for a high-level overview. A couple of changes * Report the combined cache hits/misses * Report the summary as a diagnostic note to make it more visible
Noticed this during a bit of investigation into #21, and don't necessarily expect this to fix it, but it seems correct in order to prevent the fd possibly being closed while the stream is still being read.
Remarks pollute the issue navigator in Xcode, the notes are more appropriate as offering additional details for a particular task.
…all the compiler-specific caching settings Also make the new setting, along with `COMPILATION_CACHE_ENABLE_DIAGNOSTIC_REMARKS` show up in settings UI.
Have its string representation print the actual error message for improved debuggability.
This goes in the task's output, so in the Xcode build log the user would have to expand the task output to see such detail.
|
@swift-ci test |
|
@swift-ci test linux |
matthewseaman
approved these changes
Apr 23, 2025
neonichu
approved these changes
Apr 23, 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.
No description provided.