You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "potiuk (via GitHub)" <gi...@apache.org> on 2026/08/25 14:00:57 UTC
[PR] Fix linux/arm64 CI image build broken by the ibm.db2 provider [airflow]
potiuk opened a new pull request, #72058:
URL: https://github.com/apache/airflow/pull/72058
`ibm-db` publishes no Linux aarch64 wheel and its sdist fails to build there with `NameError: name 'arch_' is not defined`, so every `linux/arm64` CI image build has failed since the ibm.db2 provider merged — blocking the scheduled ARM run on `main`.
This applies the mechanism already used for `ibm.mq`: declare `excluded-platforms` in `provider.yaml` so the provider leaves the ARM test matrix, and translate that into install-time environment markers so it is never pulled in there. `ibm-db-sa` is pure Python but depends on `ibm-db`, so it carries the same marker.
While doing so it corrects that mechanism. `EXCLUDED_PLATFORM_MACHINES` mapped `linux/arm64` to both `aarch64` and `arm64`, which is wrong in general — `platform.machine()` reports `aarch64` on Linux and `arm64` on macOS, so those are distinct targets rather than two spellings of one. IBM *does* ship `macosx_*_arm64` wheels for `ibm-db`, so excluding `arm64` would have removed a working driver from Apple Silicon for no reason. Each platform now contributes only its own machine spelling, and a provider that is unusable on every ARM target says so by listing both platforms — which is what `ibm.mq` now does. Its generated markers in the meta-package are unchanged, so that provider's behaviour is identical.
Supersedes #72021, which fixes the same build failure but leaves `ibm.db2` in the ARM test matrix.
---
##### Was generative AI tooling used to co-author this PR?
- [X] Yes — Claude Opus 5 (1M context)
Generated-by: Claude Opus 5 (1M context) following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Fix linux/arm64 CI image build broken by the ibm.db2 provider [airflow]
Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk merged PR #72058:
URL: https://github.com/apache/airflow/pull/72058
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Fix linux/arm64 CI image build broken by the ibm.db2 provider [airflow]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on PR #72058:
URL: https://github.com/apache/airflow/pull/72058#issuecomment-5424473057
### Backport failed to create: v3-3-test. View the failure log <a href='https://github.com/apache/airflow/actions/runs/32962147165'> Run details </a>
Note: As of [Merging PRs targeted for Airflow 3.X](https://github.com/apache/airflow/blob/main/dev/README_AIRFLOW3_DEV.md#merging-prs-targeted-for-airflow-3x)
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.
In matter of doubt please ask in [#release-management](https://apache-airflow.slack.com/archives/C03G9H97MM2) Slack channel.
<table>
<tr>
<th>Status</th>
<th>Branch</th>
<th>Result</th>
</tr>
<tr>
<td>❌</td>
<td>v3-3-test</td>
<td><a href="https://github.com/apache/airflow/commit/57a051997a01300b48cc6b180040418fb13b435e"><img src='https://img.shields.io/badge/Commit-57a0519-red' alt='Commit Link'></a></td>
</tr>
</table>
You can attempt to backport this manually by running:
```bash
cherry_picker 57a0519 v3-3-test
```
This should apply the commit to the v3-3-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.
After you have resolved the conflicts, you can continue the backport process by running:
```bash
cherry_picker --continue
```
If you don't have cherry-picker installed, see the [installation guide](https://github.com/apache/airflow/blob/main/dev/README.md#how-to-backport-pr-with-cherry-picker-cli).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org