-
Notifications
You must be signed in to change notification settings - Fork 112
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
Catch CI up with github #577
Conversation
ubuntu-latest no longer has clang-10 available as of https://github.blog/changelog/2022-11-09-github-actions-ubuntu-latest-workflows-will-use-ubuntu-22-04/ FIXES #575
Work around #576
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.
LGTM. If it not to much trouble, could you add a comment about why we aren't using latest. I guess we could evolve some tests to a later clang?
No trouble at all. If you want to pick a |
Don't merge; testing newer clangs. If it works, I'll expand some commentary and then we can merge. |
C++20 accidentally deprecated ATOMIC_FLAG_INIT, but in C++17 this is the only way to reliably initialize an atomic_flag to a known value. See https://en.cppreference.com/w/cpp/atomic/ATOMIC_FLAG_INIT
- Copy and shift our clang-10-specific variant tests onto the latest - Additionally add 20.04 as a test point, along-side 18.04
OK, maybe ready now. :) |
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.
LGTM, thanks
Fallout from https://github.blog/changelog/2022-11-09-github-actions-ubuntu-latest-workflows-will-use-ubuntu-22-04/