-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
macOS binary is not x86_64 but arm64 #1687
Comments
Hi @drazisil-codecov - after updating our self-hosted instance to v24.8.1 or v24.9.3 the mac uploader is failing due to this. Would you know if the mac uploader would be set to v0.7.3 in a future version of codecov? As far as I understand this was implemented with shotgunsoftware/tk-ci-tools#53, but it seems that latest v24.9.3 still uses v0.8.0. Thank you! |
Hi @nikosatwork , You are referring to the copy in the self-hosted? |
Hi, yes |
We're having the same issue on Github Actions, as the runners are x86 based. For now we're rolling back and using Building a fat binary is definitely the way to go here. 👍 Also, swapping from one architecture to the other without warning in a minor release isn't great. |
Hi @drazisil-codecov. Are there any updates on this? Thank you. |
(cc: @rohan-at-sentry |
Hi @nikosatwork can you please try using the CLI? https://docs.codecov.com/docs/codecov-uploader |
Describe the bug
In Azure Pipelines CI, our pipeline breaks because the runner machines are x86_64 (intel) and not apple silicon (arm64) on v0.8.0.
v0.7.3 is x86_64 for reference. Is it possible to build a fat binary?
To Reproduce
Steps to reproduce the behavior:
lipo -archs codecov
Expected behavior
Have a fat binary that bundles x86_64 and arm64 architectures.
The text was updated successfully, but these errors were encountered: