-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Enable concurrency back deployment in CI configurations #39061
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
Enable concurrency back deployment in CI configurations #39061
Conversation
@swift-ci please build toolchain |
@swift-ci please test |
Linux Toolchain (Ubuntu 16.04) Install command |
macOS Toolchain Install command |
@swift-ci please test Windows |
a5d40db
to
f2d96c3
Compare
@swift-ci please test |
@swift-ci please build toolchain |
Linux Toolchain (Ubuntu 16.04) Install command |
Build failed |
@swift-ci please test source compatibility |
@swift-ci please test Linux |
Build failed |
Build failed |
f2d96c3
to
61c8f86
Compare
@swift-ci please test |
@swift-ci please build toolchain |
@swift-ci please test source compatibility |
Linux Toolchain (Ubuntu 16.04) Install command |
macOS Toolchain Install command |
We're not getting the library installed properly, so this is not ready. |
Allow the installation of the back-deployment shared libraries for concurrency via build-script.
@swift-ci please build toolchain |
@swift-ci please smoke test |
@swift-ci please test source compatibility |
All Python failures. Grrrr |
@swift-ci please test |
@swift-ci please build toolchain |
@swift-ci please test source compatibility |
… name When linking against the back-deployed _Concurrency library, ensure that clients record an `@rpath`-relative dependency.
Linux Toolchain (Ubuntu 16.04) Install command |
When testing the runtime in the OS (via the lit parameter `use_os_stdlib`), add the path to the back-deployed concurrency libraries into `DYLD_LIBRARY_PATH` for the test run. This should allow us to run our regression tests on older OS's.
macOS Toolchain Install command |
build-script-impl effectively ignores the `install_destdir` provided to it by build-toolchain, and uses something based on the build subdir instead. But build-script products do follow `install_destdir`, so make `build-toolchain` provide something closer to correct.
@swift-ci please build toolchain |
@swift-ci please test |
macOS Toolchain Install command |
Enable concurrency back deployment in the CI configurations so we can test it more thoroughly and build toolchains