This PR starts using the new M1 macOS runner.
The alternative approach might be using a matrix, but it is not trivial to implement.
584 | @@ -585,10 +585,10 @@ jobs: 585 | run: env 586 | if: ${{ always() }} 587 | 588 | - macos-native: 589 | - name: "x86_64: macOS Monterey" 590 | + x86_64-macos-native: 591 | + name: "x86_64: macOS Monterey, Valgrind"
Did you remove the "Valgrind" intentionally?
No, I mean you have removed the substring ", Valgrind" from the job name. :D
Sorry, I don't follow... The diff appends the substring ", Valgrind" to the job name, no?
Lol sure, sorry, nevermind...
Concept ACK
It's a bit sad that we can't run Valgrind on the new machines yet.
I think it will be good to add an MSan job with ctimetests enabled. We have an arm64 job with Valgrind on Linux (Cirrus CI), but I guess having a ctimetest for macOS (Apple clang) can't hurt.
I think it will be good to add an MSan job with ctimetests enabled. We have an arm64 job with Valgrind on Linux (Cirrus CI), but I guess having a ctimetest for macOS (Apple clang) can't hurt.
For both Apple Clang and LLVM Clang, I have:
clang: error: unsupported option '-fsanitize=memory' for target 'arm64-apple-darwin23.5.0'
Ok, damn, I didn't know that MSan is not supported on macOS... https://github.com/google/sanitizers/issues/588
ACK 218f0cc93bd77eae926f4c4e259951b92bf00aec