-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Re-apply "Tests: enable Swift PM tests in Windows toolchain build"" #82274
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
base: main
Are you sure you want to change the base?
Re-apply "Tests: enable Swift PM tests in Windows toolchain build"" #82274
Conversation
@swift-ci smoke test |
1 similar comment
@swift-ci smoke test |
Windows platform build failed with Trying again @swift-ci smoke test windows |
Windows Platform build failed with Between this and the previous execution, the test that hangs in non-deterministic. |
@swift-ci smoke test windows |
without code changes, the Windows platform build failed
|
@swift-ci test windows |
1 similar comment
@swift-ci test windows |
In its current state, this is adding ~65m to the overall test time, which might be a bit excessive. I have a set of patches up which need some help to get merged, but bring this time down to ~8m. |
I'm in favour of submitting this, once the test are passing, and then working on the other changes to bring the time down. This will ensure other changes that execute this script will execute the SwiftPM tests as well, helping to ensure regressions are not introduced. Can you please share the PRs that bring this time down? |
Adding comment for automatic GitHub traceability. This PR fixes: swiftlang/swift-package-manager#8895 |
swiftlang/swift-package-manager#8891 @swift-ci smoke test |
34cd647
to
0bb3d3d
Compare
swiftlang/swift-package-manager#8899 @swift-ci smoke test |
It looks like the Swift Test Windows Platform has test hangs
|
swiftlang/swift-package-manager#8899 @swift-ci smoke test |
swiftlang/swift-package-manager#8899 @swift-ci smoke test |
swiftlang/swift-package-manager#8899 @swift-ci smoke test macOS |
2 similar comments
swiftlang/swift-package-manager#8899 @swift-ci smoke test macOS |
swiftlang/swift-package-manager#8899 @swift-ci smoke test macOS |
swiftlang/swift-package-manager#8899 @swift-ci smoke test macOS |
The SwiftPM PR was rebased. so re-run all the pipelines. swiftlang/swift-package-manager#8899 @swift-ci smoke test |
he SwiftPM PR was updated. so re-run all the pipelines. swiftlang/swift-package-manager#8899 @swift-ci smoke test |
The SwiftPM PR was updated, so run all pipelines swiftlang/swift-package-manager#8899 @swift-ci smoke test |
1 similar comment
The SwiftPM PR was updated, so run all pipelines swiftlang/swift-package-manager#8899 @swift-ci smoke test |
swiftlang/swift-package-manager#8899 @swift-ci smoke test windows |
Update test expectation for executing SwiftPM tests in the Windows Platform Test PR build - the script found in https://github.com/swiftlang/swift/blob/main/utils/build.ps1. Relates to: swiftlang/swift#82274 Relates to: #8895 Depends on: #8975
Dependent PR has been merged. so let's run the testing again @swift-ci test |
This is adding an hour to the Windows CI job (it's now 6 hours). When you rerun to address the Linux and macOS failures, can we rerun the Windows too to double check? |
The two build failures are not required and they haven't been run in a while. With that said, my plan was to retriever the required build before merging to ensure the builds still pass. |
@swift-ci test |
@swift-ci smoke test |
Reverts #82265, which re-applies #80405 Enable the SwiftPM tests in the Windows toolchain build to get extra confidence the change did not introduce any regression on the Windows platform. Fixes: swiftlang/swift-package-manager#8895
0bb3d3d
to
3ac47b8
Compare
@swift-ci smoke test |
@compnerd, @shahmishal : could you please review this? This change seems to add 1 hours to the Windows platform build. |
This is adding ~45m to the build:
This puts it in third place, which is pretty big. I think that @ahoppen had a new trick up his sleeve (using Xcode multi-space workspaces) to reduce the |
The foundation regression most likely is coming from #83572 |
Before merging this PR, I would like to understand which tests are taking the longest. |
Agreed. I am wondering if it's the integration tests which call "swift build". Those probably could be done in a nightly regression run instead of on every toolchain build. Just a possibility. We're also looking forward to completing the SwiftBuild build system transition which I believe will give us build performance that is as good or better than CMake/Ninja. At least that's a goal which would allow us to unify the builds of at least the Swift packages in the toolchain. I'd rather not throw in short term changes that would just make maintenance of the builds even harder. |
Reverts #82265, which re-applies #80405
Enable the SwiftPM tests in the Windows toolchain build to get extra confidence the change did not introduce any regression on the Windows platform.
In addition to the re-application of #80405, execute SwiftPM tesst in parallel
Fixes: swiftlang/swift-package-manager#8895
Depends on: swiftlang/swift-package-manager#8899