There shouldn't be any downside, because XCode remains pinned to the same version.
However, builds are expected to be a bit faster with M1, which seems nice.
There shouldn't be any downside, because XCode remains pinned to the same version.
However, builds are expected to be a bit faster with M1, which seems nice.
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--006a51241073e994b41acfe9ec718e94-->
For detailed information about the code coverage, see the test coverage report.
<!--021abf342d371248e50ceaed478a90ca-->
See the guideline for information on the review process.
| Type | Reviewers |
|---|---|
| ACK | hebasto, willcl-ark |
If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update.
Apple clang version 15.0.0 (clang-1500.0.40.1)
Target: x86_64-apple-darwin22.6.0
Thread model: posix
InstalledDir: /Applications/Xcode_15.0.1.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
Apple clang version 15.0.0 (clang-1500.0.40.1)
Target: arm64-apple-darwin23.6.0
Thread model: posix
InstalledDir: /Applications/Xcode_15.0.1.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
73 | @@ -74,11 +74,11 @@ jobs: 74 | # Use clang++, because it is a bit faster and uses less memory than g++ 75 | git rebase --exec "echo Running test-one-commit on \$( git log -1 ) && CC=clang CXX=clang++ cmake -B build -DWITH_ZMQ=ON -DBUILD_GUI=ON -DBUILD_BENCH=ON -DBUILD_FUZZ_BINARY=ON -DWITH_BDB=ON -DWITH_NATPMP=ON -DWITH_MINIUPNPC=ON -DWITH_USDT=ON && cmake --build build -j $(nproc) && ctest --test-dir build -j $(nproc) && ./build/test/functional/test_runner.py -j $(( $(nproc) * 2 ))" ${{ env.TEST_BASE }} 76 | 77 | - macos-native-x86_64: 78 | - name: 'macOS 13 native, x86_64, no depends, sqlite only, gui' 79 | + macos-native-arm64:
This is still building using x86_64-apple-darwin as the host (from 00_setup_env_mac_native.sh). I wonder if the "native" here is therefore confusing?
That sounds like a bug in the CI config. However, it should be harmless, because HOST is unused (apart from a folder naming), because depends isn't used here.
I'll add an unrelated bugfix commit to remove the wrong config value.
Concept ACK.
Very much in favour of speeding these jobs up! Changes look good to me so far, just one Q on the jobname with this change in architecture.
The HOST is wrong, because this is a native build, where the HOST is
supposed to be auto-detected.
Concept ACK.
Perhaps explicitly mention the switch from the x86_64 architecture to arm64?
Perhaps explicitly mention the switch from the
x86_64architecture toarm64?
Sure, done
ACK fab932b4211ea0a4c10e484c08042552f9c58c15