-
Notifications
You must be signed in to change notification settings - Fork 295
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cherry pick recent fixes to release/1.0 in preparation of tagging 1.0.3 #168
Conversation
lorentey
commented
Sep 1, 2022
- [OrderedDictionary][doc] Update docs for merge/filter operations #153: [OrderedDictionary][doc] Update docs for merge/filter operations
- Remove Swift PM Artifacts to avoid Generated Schemes in Xcode #155: Remove Swift PM Artifacts to avoid Generated Schemes in Xcode
- Reinstate custom schemes under Utils/swift-collections.xcworkspace #156: Reinstate custom schemes under Utils/swift-collections.xcworkspace
- [Xcode] Update schemes & file template #161: [Xcode] Update schemes & file template
- [OrderedCollection] Use standard temp allocation facility, if available #160: [OrderedCollection] Use standard temp allocation facility, if available
- [OrderedSet] Work around weird name lookup issue in compiler #162: [OrderedSet] Work around weird name lookup issue in compiler
- Force-inline _modify accessors to work around a performance issue #165: Force-inline _modify accessors to work around a performance issue
(cherry picked from commit 480b0af)
(cherry picked from commit 7016a13)
(cherry picked from commit 3fce10a)
(cherry picked from commit 00a99aa)
Update Collections scheme with support for testing. Update the copyright year in file template. (cherry picked from commit 3437abe)
The 5.6 stdlib introduced a new facility for temporary allocations that promises better performance than direct allocations. Use it when the toolchain version is above 5.6. (cherry picked from commit ddb6d14)
(cherry picked from commit 0a26362)
(cherry picked from commit c82261a)
(cherry picked from commit ee1b2de)
(#165 has not landed on main yet, but I want to get a head start with validation) |
Temporarily pulling in #169 as well. |
Full test results with Xcode 14 beta 6 on macOS 13:
|
Full test results on Ubuntu 20.04 / arm64 / Swift 5.6.2:
|
Full test results on Ubuntu 20.04 / arm64 / Swift 5.8 nightly as of today:
|
Full test results on Ubuntu 20.04 / arm64 / Swift main nightly as of today:
|
macOS 13 / AS / Xcode 14 beta 6
|
Manual tests on Windows 10, x86_64, Swift 5.6.1 passing:
|
Windows 10, x86_64, Swift 5.8 nightly
|
Windows 10, x86_64, Swift 5.7 nightly
|
macOS 12.5, arm64, Swift 5.6.1 The failure on Mac Catalyst is due to a toolchain issue.
|
macOS 12.5, arm64, Xcode 12.4 (Swift 5.3.2) Simulator & Catalyst failures are expected on this setup.
|
macOS 12.5, x86_64, Xcode 13.4.1 (Swift 5.6.1)
|
macOS 12.5, x86_64, 12.4 (Swift 5.3.2) watchOS/tvOS failures are expected in this configuration.
|
macOS 12.5, arm64, 12.5.1 (Swift 5.4.2) The Mac Catalyst + iOS Simulator failures aren't cause for worry here.
|
macOS 12.5, x86_64, Xcode 12.5.1 (Swift 5.4.2) The iOS Simulator failure isn't cause for worry here.
|
macOS 12.5, arm64, Xcode 13.2.1 (Swift 5.5.2)
|
macOS 12.5, x86_64, Xcode 13.2.1 (Swift 5.5.2)
|
Ubuntu 20.04, x86_64, Swift 5.7 nightly
|
Ubuntu 20.04, x86_64, Swift 5.3.3
|
Ubuntu 20.04, x86_64, Swift 5.8 nightly Not sure why this identifies itself as 5.7 ¯_(ツ)_/¯
|
Ubuntu 20.04, x86_64, Swift 5.4.3
|
Ubuntu 20.04, x86_64, Swift 5.5.3
|
Ubuntu 20.04, x86_64, Swift 5.6.2
|
That's enough testing for me. |
bf20c7a
to
b379fa7
Compare
@swift-ci test |
(force pushed to remove cherry pick of #169, which has landed on release/1.0 now.) |