macOS binary is not x86_64 but arm64

[carlos-villavicencio-adsk]

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:

1. Get https://uploader.codecov.io/v0.8.0/macos/codecov
2. On macOS execute lipo -archs codecov
3. See the architecture type.

Expected behavior
Have a fat binary that bundles x86_64 and arm64 architectures.

[nikosatwork]

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!

[drazisil-codecov]

Hi @nikosatwork ,

You are referring to the copy in the self-hosted?

[nikosatwork]

Hi, yes

[paulofierro]

We're having the same issue on Github Actions, as the runners are x86 based. For now we're rolling back and using 0.7.3 of the uploader as that is built for x86_64.

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.

[nikosatwork]

Hi @drazisil-codecov. Are there any updates on this? Thank you.

[drazisil-codecov]

(cc: @rohan-at-sentry

[drazisil-codecov]

Hi @nikosatwork can you please try using the CLI? https://docs.codecov.com/docs/codecov-uploader

[nikosatwork]

@drazisil-codecov will do. In the meantime, could you please point me to the location of the uploader in the pod so we could replace it with v0.7.3 (i.e. where can we find codecov.domain.com/uploader?) Thank you.

[drazisil-codecov]

Hi @nikosatwork ,

I believe it's here https://github.com/codecov/gazebo/blob/bd8b644fff48fc5bcdd06ed1ac1170b258b847da/docker/nginx-no-ipv6.conf#L51-L54