Build osx-arm64 natively on Azure arm64 agents - #17
Conversation
conda-forge now offers native Apple Silicon macOS agents on Azure
(conda-forge.github.io#1781), so enable osx-arm64 via `provider: {osx_arm64:
default}` rather than cross-compiling from osx-64. A native build avoids the
cross-compile issues (Bad CPU type, host pkg-config, numpy lookup) and runs the
test suite on arm64.
Bump build number 0 -> 1: 3.3.7 build 0 is already published for linux-64,
osx-64 and win-64, so rebuilding to add osx-arm64 needs a new build number for
the rebuilt artifacts to upload.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( I do have some suggestions for making it better though... For recipe/meta.yaml:
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/27085871146. Examine the logs at this URL for more detail. |
|
@conda-forge-admin, please rerender |
…2026.06.07.05.41.4
The native osx-arm64 jobs failed provisioning the base env: the micromamba download returned a 92-byte "504 Gateway Time-out" page instead of the binary, so bash failed executing it. Unrelated to the build; retrigger. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Hi! This is the friendly automated conda-forge-linting service. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipe/meta.yaml:
For recipe/meta.yaml:
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/27086023124. Examine the logs at this URL for more detail. |
Native osx-arm64 builds succeed; a couple of jobs intermittently fail fetching micromamba (504 from the releases CDN) during base-env provisioning. Retrigger the pipeline; unrelated to the build. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( I do have some suggestions for making it better though... For recipe/meta.yaml:
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/27086316672. Examine the logs at this URL for more detail. |
Addresses the conda-forge lint note about a host requirement overriding the feedstock pinning. Build number stays 1 (this build is not yet published). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
@conda-forge-admin, please lint |
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
Enables native osx-arm64 builds.
conda-forge now provides native Apple Silicon macOS agents on Azure Pipelines (see conda-forge/conda-forge.github.io#1781), so this switches osx-arm64 on via:
rather than cross-compiling from osx-64 (
build_platform: {osx_arm64: osx_64}). A native build runs on a real arm64 mac, so it avoids the cross-compilation issues this recipe hits when cross-compiled (the meson build resolves numpy via pkg-config, which doesn't work for the host machine in a cross build), and it runs the test suite natively on arm64.The build number is bumped
0 -> 1because 3.3.7 build 0 is already published for linux-64/osx-64/win-64; rebuilding to add osx-arm64 re-runs all platforms, so the rebuilt artifacts need a new build number to upload.I'll request a rerender to generate the osx_arm64 variant.
cc @conda-forge/anuga