Repository navigation
Fix linux/arm64 CI image build broken by the ibm.db2 provider - #72058
Merged
potiuk merged 1 commit intoAug 26, 2026
Merged
Conversation
`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 provider merged, blocking the scheduled ARM run on main. Apply the mechanism already used for ibm.mq — declare `excluded-platforms` so the provider leaves the ARM test matrix, and translate that into install-time markers so it is never pulled in there. `ibm-db-sa` is pure Python but depends on `ibm-db`, so it needs the same marker. That mechanism mapped `linux/arm64` to both `aarch64` and `arm64`, which is wrong in general: `platform.machine()` reports `aarch64` on Linux and `arm64` on macOS, so the two 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. Each platform now contributes only its own machine spelling, and a provider unusable on every ARM target says so by listing both platforms — which is what ibm.mq now does, leaving its generated markers unchanged.
potiuk
requested review from
amoghrajesh,
ashb,
bugraoz93,
choo121600,
dabla,
ephraimbuddy,
gopidesupavan,
jason810496,
jedcunningham,
jscheffl and
vatsrahul1001
as code owners
August 25, 2026 14:00
1 task done
FrankYang0529
approved these changes
Aug 26, 2026
amoghrajesh
approved these changes
Aug 26, 2026
Contributor
Backport failed to create: v3-3-test. View the failure log Run detailsNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
You can attempt to backport this manually by running: cherry_picker 57a0519 v3-3-testThis should apply the commit to the v3-3-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continueIf you don't have cherry-picker installed, see the installation guide. |
imrichardwu
pushed a commit
to imrichardwu/airflow
that referenced
this pull request
Sep 11, 2026
…#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 provider merged, blocking the scheduled ARM run on main. Apply the mechanism already used for ibm.mq — declare `excluded-platforms` so the provider leaves the ARM test matrix, and translate that into install-time markers so it is never pulled in there. `ibm-db-sa` is pure Python but depends on `ibm-db`, so it needs the same marker. That mechanism mapped `linux/arm64` to both `aarch64` and `arm64`, which is wrong in general: `platform.machine()` reports `aarch64` on Linux and `arm64` on macOS, so the two 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. Each platform now contributes only its own machine spelling, and a provider unusable on every ARM target says so by listing both platforms — which is what ibm.mq now does, leaving its generated markers unchanged.
1 task done
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ibm-dbpublishes no Linux aarch64 wheel and its sdist fails to build there withNameError: name 'arch_' is not defined, so everylinux/arm64CI image build has failed since the ibm.db2 provider merged — blocking the scheduled ARM run onmain.This applies the mechanism already used for
ibm.mq: declareexcluded-platformsinprovider.yamlso the provider leaves the ARM test matrix, and translate that into install-time environment markers so it is never pulled in there.ibm-db-sais pure Python but depends onibm-db, so it carries the same marker.While doing so it corrects that mechanism.
EXCLUDED_PLATFORM_MACHINESmappedlinux/arm64to bothaarch64andarm64, which is wrong in general —platform.machine()reportsaarch64on Linux andarm64on macOS, so those are distinct targets rather than two spellings of one. IBM does shipmacosx_*_arm64wheels foribm-db, so excludingarm64would 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 whatibm.mqnow 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.db2in the ARM test matrix.Was generative AI tooling used to co-author this PR?
Generated-by: Claude Opus 5 (1M context) following the guidelines