Move CI runners away from macOS-10.15 because of sunsetting by Github.
#7028
Conversation
There's a scheduled removal of the image by 30 Aug 2022, with intermittent failing of those runners to raise awareness to that effect. We need to move our CI runners to at least `macOS-11` to preempt any failures. Fixes diffblue#7027.
| check-macos-11-make-clang: | ||
| runs-on: macos-11 |
There was a problem hiding this comment.
Should we then perhaps get rid of check-macos-11-cmake-clang and be content that we have a make-based test for macOS 11 and a CMake-based test for macOS 12?
There was a problem hiding this comment.
I diffed the two jobs, and they are essentially the same:
fotiskoutoulakis@192 ~ % diff /tmp/12.yml /tmp/11.yml
1,2c1,2
< check-macos-12-cmake-clang:
< runs-on: macos-12
---
> check-macos-11-cmake-clang:
> runs-on: macos-11So, the only difference I would reckon is the system toolchain (and other environment parameters), which if they are appropriately exercised by the cmake build, then I don't see any reason to keep it.
There was a problem hiding this comment.
Actually, I went ahead and did just that.
At this point, we have a `cmake` build on both macOS 11 and 12. It makes more sense to drop one of them (`11`), given that the environment and toolchain are exercised by the `make` job on the same platform. That allows us to simplify our CI pipeline.
NlightNFotis
force-pushed
the
move_ci_runners_macos_11
branch
from
06c9589 to
156e28e
Compare
Codecov Report
@@ Coverage Diff @@
## develop #7028 +/- ##
========================================
Coverage 77.88% 77.88%
========================================
Files 1569 1569
Lines 180892 180892
========================================
Hits 140880 140880
Misses 40012 40012 Continue to review full report at Codecov.
|
There's a scheduled removal of the image by 30 Aug 2022, with intermittent
failing of those runners to raise awareness to that effect. We need to
move our CI runners to at least
macOS-11to preempt any failures.Fixes #7027.