Use Perforce arm64 binary on macOS CI jobs
The previous step replaced deprecated macos-13 image with macos-14 image on GitHub Actions CI. While x86-64 binaries can work there, because macos-14 images are arm64 based (we could replace it with macos-14-large that is x86-64), it makes more sense to use arm64 binary there. Without this change, we have been getting unusually higher rate of failures from random macOS CI jobs railing to run t98xx series of tests. Helped-by: Koji Nakamaru <koji.nakamaru@gree.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>main
parent
73b9cdb7c4
commit
ffff0bb0da
|
|
@ -103,7 +103,7 @@ macos-*)
|
||||||
brew link --force gettext
|
brew link --force gettext
|
||||||
|
|
||||||
mkdir -p "$CUSTOM_PATH"
|
mkdir -p "$CUSTOM_PATH"
|
||||||
wget -q "$P4WHENCE/bin.macosx1015x86_64/helix-core-server.tgz" &&
|
wget -q "$P4WHENCE/bin.macosx12arm64/helix-core-server.tgz" &&
|
||||||
tar -xf helix-core-server.tgz -C "$CUSTOM_PATH" p4 p4d &&
|
tar -xf helix-core-server.tgz -C "$CUSTOM_PATH" p4 p4d &&
|
||||||
sudo xattr -d com.apple.quarantine "$CUSTOM_PATH/p4" "$CUSTOM_PATH/p4d" 2>/dev/null || true
|
sudo xattr -d com.apple.quarantine "$CUSTOM_PATH/p4" "$CUSTOM_PATH/p4d" 2>/dev/null || true
|
||||||
rm helix-core-server.tgz
|
rm helix-core-server.tgz
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue