-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
CI: use clang16 nightly builds #469
Conversation
Looking forward to those results, although at this point nothing interesting should happen ... |
c++20 needs a newer version of catch2 |
04a6da0
to
a114b70
Compare
…h2 v3 version for internal
key4hep stack still fails, now complaining about too old catch2
What do you want to do about this: Abort? Retry? Ignore? |
Co-authored-by: Thomas Madlener <thomas.madlener@desy.de>
No |
So just drop the key4hep-release based build you mean? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good now. Just need to remember to re-enable the key4hep release once it can be used again.
Thanks for taking care of this.
* CI: use clang16 nightly builds * CI: linux: add CXX_STANDARD variable and set for builds * Tests: require newer catch2 version when using c++20, get latest catch2 v3 version for internal * CI: key4hep use AUTO for catch2 * CI: disable key4hep release based build
* CI: use clang16 nightly builds * CI: linux: add CXX_STANDARD variable and set for builds * Tests: require newer catch2 version when using c++20, get latest catch2 v3 version for internal * CI: key4hep use AUTO for catch2 * CI: disable key4hep release based build
BEGINRELEASENOTES
tabulate
available)ENDRELEASENOTES
Hmm: these nightly builds are with c++20...