-
Notifications
You must be signed in to change notification settings - Fork 74
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
CI update #1713
CI update #1713
Conversation
Wow, case in point: One of our C++20 jobs is failing with Boost 1.79.0. Apparently Boost.fiber is internally using From Boost.fiber's documentation:
So I guess we need to start thinking about the future of this back-end. |
That was fixed 15 days ago: boostorg/fiber@a6b64c9 However, that still leaves Boost.Fiber 1.79 and below problematic with C++20. |
It seems 2022-05-10T17:06:01.9941211Z +++ sudo update-alternatives --install /usr/bin/g++ g++ /usr/bin/g++-12 50
2022-05-10T17:06:01.9987407Z update-alternatives: error: alternative path /usr/bin/g++-12 doesn't exist |
You're right. |
Rebased and added the following changes:
|
f1daaad
to
ddf34f2
Compare
|
6c0e896
to
2a37179
Compare
While you are at it: Could you please change the build type of check with enabled sanitizer which are currently |
Done. |
d4ba909
to
125f774
Compare
eb018e6
to
40e920e
Compare
I am a little bit unhappy that this PR is mixing features, refactorings, and adding new test combinations. Could you split e.g CUDA keyring refactorings, job renamings and new jobs into separate PRs? This would also simplify the review and give us a better overview of why a CI job is failing. |
And so it shall be done. I will prepare a number of successor PRs and close this one afterwards. |
All points from the original description have been addressed. |
Summary:
added gcc-12 to CI- handled in Add gcc-12 to CI #1765added clang-14 to CI- handled in Add clang-14 to CI #1766added Xcode 13.3.1 to CI -> we now support macOS 12 "Monterey"- handled in CI Update for macOS #1759added CUDA 11.7 to CI- handled in CUDA CI update #1890CUDA 11.6 tests now use CUDA 11.6.2- handled in CUDA CI update #1890collapsed compiler support matrix- handled in Collapse compiler matrix #1860fixed a few consistency issues for the clang-cuda device compiler (the matrix showed support for CUDA versions that clang itself doesn't officially support yet)- handled in CUDA CI update #1890added CUDA 11.6 + gcc-11 job to GitLab CI- handled in CUDA CI update #1890added ROCm 5.1 jobs to GitLab CI- handled in CI Update for ROCm #1762.added Boost 1.79.0 to CI- handled in Update CMake and Boost point releases #1903added CMake 3.23.x to CI- handled in Update CMake and Boost point releases #1903updated older CMake versions to latest point releases- handled in Update CMake and Boost point releases #1903removed all occurrences of- handled in Enable more C++20 jobs #1902alpaka_CXX_STANDARD: 17
from the GitHub CI script since that is now our defaultadded a few occurrences of- handled in Enable more C++20 jobs #1902alpaka_CXX_STANDARD: 20
to the GitHub CI scriptgcc-12 jobs will use GitHub's- handled in Add gcc-12 to CI #1765ubuntu-22.04
runnersIf sanitizers are enabled, clang jobs will install the llvm base package. This includes the- handled in Simplify clang installation #1763llvm-symbolizer
binary required for meaningful output.If the Boost.fiber back-end is enabled in C++20 mode CMake will print an error and abort (see [RFC] Future of the Boost.fiber back-end #1714).- superseded by Drop Boost.fiber back-end #1718Disabled the address sanitizer for- needs more investigationmemBufTest
if clang-14 is used (see clang-16: ASan fails formemBufTest
. #1753).Removed Xcode 12.4.0 from the CI -> we will no longer support macOS 10.15 "Catalina"- handled in CI Update for macOS #1759.Fixes #1670. Fixes #1708. Fixes #1724.