macos-arm64 build is actually x86_64 #2960
Description
Describe the bug
As of v2.73.2, all macos arm64 builds are actually x86_64 binaries:
jfrog-mac-arm64-2.72.0: Mach-O 64-bit arm64 executable, flags:<|DYLDLINK|PIE>
jfrog-mac-arm64-2.72.1: Mach-O 64-bit arm64 executable, flags:<|DYLDLINK|PIE>
jfrog-mac-arm64-2.72.2: Mach-O 64-bit arm64 executable, flags:<|DYLDLINK|PIE>
jfrog-mac-arm64-2.72.3: Mach-O 64-bit arm64 executable, flags:<|DYLDLINK|PIE>
jfrog-mac-arm64-2.72.4: Mach-O 64-bit arm64 executable, flags:<|DYLDLINK|PIE>
jfrog-mac-arm64-2.72.5: Mach-O 64-bit arm64 executable, flags:<|DYLDLINK|PIE>
jfrog-mac-arm64-2.73.0: Mach-O 64-bit arm64 executable, flags:<|DYLDLINK|PIE>
jfrog-mac-arm64-2.73.2: Mach-O 64-bit x86_64 executable, flags:<|DYLDLINK|PIE>
jfrog-mac-arm64-2.73.3: Mach-O 64-bit x86_64 executable, flags:<|DYLDLINK|PIE>
jfrog-mac-arm64-2.74.0: Mach-O 64-bit x86_64 executable, flags:<|DYLDLINK|PIE>
jfrog-mac-arm64-2.74.1: Mach-O 64-bit x86_64 executable, flags:<|DYLDLINK|PIE>
jfrog-mac-arm64-2.75.0: Mach-O 64-bit x86_64 executable, flags:<|DYLDLINK|PIE>
(downloaded from https://releases.jfrog.io/artifactory/jfrog-cli/v2/$VERSION/jfrog-cli-mac-arm64/jfrog and ran file against the executable)
This obviously fails to run due to the different CPU architecture
Current behavior
When running the jfrog/setup-jfrog-cli action on an arm64 mac, we were getting the following error:
Setup JFrog CLI
Found JFrog CLI in cache. No need to download
/Users/Shared/actions-runner/_work/_tool/jf/2.74.1/arm64/jf config add setup-jfrog-cli-server --url <artifactory url> --interactive=false --overwrite=true --access-token ***
node:internal/child_process:420
throw new ErrnoException(err, 'spawn');
^
Error: spawn Unknown system error -86
at ChildProcess.spawn (node:internal/child_process:420:11)
at Object.spawn (node:child_process:762:9)
at ToolRunner.<anonymous> (/Users/Shared/actions-runner/_work/_actions/jfrog/setup-jfrog-cli/v4/node_modules/@actions/exec/lib/toolrunner.js:413:34)
at Generator.next (<anonymous>)
at /Users/Shared/actions-runner/_work/_actions/jfrog/setup-jfrog-cli/v4/node_modules/@actions/exec/lib/toolrunner.js:27:71
at new Promise (<anonymous>)
at __awaiter (/Users/Shared/actions-runner/_work/_actions/jfrog/setup-jfrog-cli/v4/node_modules/@actions/exec/lib/toolrunner.js:23:12)
at /Users/Shared/actions-runner/_work/_actions/jfrog/setup-jfrog-cli/v4/node_modules/@actions/exec/lib/toolrunner.js:395:53
at new Promise (<anonymous>)
at ToolRunner.<anonymous> (/Users/Shared/actions-runner/_work/_actions/jfrog/setup-jfrog-cli/v4/node_modules/@actions/exec/lib/toolrunner.js:395:20) {
errno: -86,
code: 'Unknown system error -86',
syscall: 'spawn'
}
Node.js v20.19.0
We tried running the downloaded binary manually and got:
exec: Failed to execute process './jfrog-mac-arm64-2.73.2': Bad CPU type in executable.
Reproduction steps
Download https://releases.jfrog.io/artifactory/jfrog-cli/v2/2.74.1/jfrog-cli-mac-arm64/jfrog and try to run it on an arm64 mac.
Expected behavior
The arm64 binary should actually be an arm64 binary.
JFrog CLI version
v2.73.2 and later
Operating system type and version
macos on arm64
JFrog Artifactory version
No response
JFrog Xray version
No response