FrankYang0529 opened a new pull request, #70015: URL: https://github.com/apache/airflow/pull/70015
## Why - The `main` branch still queries a workflow that stopped running two months ago. runner_type calls get_job_label(), which looks up the run history of ci-amd-arm.yml (a file deleted from main by #66348. GitHub retains run history for deleted workflows, so the query still succeeds and returns the last run: [25523746003](https://github.com/apache/airflow/actions/runs/25523746003). Its Basic tests label is `ubuntu-22.04` (AMD), which `RUNNERS_TYPE_CROSS_MAPPING` then inverts into ARM. Every selective-check run on main since has reported ARM on both wrappers (ci-amd.yml and ci-arm.yml). - So main lost kerberos and ibm.mq coverage on AMD for two months. The AMD canary believes it is on ARM, so `DISABLE_TESTABLE_INTEGRATIONS_FROM_ARM` disables kerberos and ibm.mq. <img width="1300" height="626" alt="Screenshot 2026-07-17 at 9 53 28 PM" src="https://github.com/user-attachments/assets/f821ef6a-a114-4440-ba26-c8232808cd4b"; /> ## How - The `build-info` step cannot detect the platform it is planning for. It runs on `ubuntu-22.04` in both wrappers (ci-amd.yml and ci-arm.yml). Reading the machine's own architecture would therefore always answer "AMD". This PR introduces `PLATFORM` environment variable on their `selective-checks` step. The `PLATFORM` helps to select which provider will be run in `tests-core-integration`. - Remove the stale `get_job_label` and `RUNNERS_TYPE_CROSS_MAPPING`. ## Verification - Run `PLATFORM=linux/arm64 breeze ci selective-check --github-event-name schedule --github-context '{"ref_name":"main"}' --pr-labels '["full tests needed"]'`. There is no `kerberos` in `testable-core-integrations`. - Run `PLATFORM=linux/amd64 breeze ci selective-check --github-event-name schedule --github-context '{"ref_name":"main"}' --pr-labels '["full tests needed"]'`. The `kerberos` is in `testable-core-integrations`. <!-- SPDX-License-Identifier: Apache-2.0 https://www.apache.org/licenses/LICENSE-2.0 --> <!-- Thank you for contributing! Please provide above a brief description of the changes made in this pull request. Write a good git commit message following this guide: http://chris.beams.io/posts/git-commit/ Please make sure that your code changes are covered with tests. And in case of new features or big changes remember to adjust the documentation. For user-facing UI changes, please attach before/after screenshots (or a short screen recording) so reviewers can assess the visual impact. Feel free to ping (in general) for the review if you do not see reaction for a few days (72 Hours is the minimum reaction time you can expect from volunteers) - we sometimes miss notifications. In case of an existing issue, reference it using one of the following: * closes: #ISSUE * related: #ISSUE --> --- ##### Was generative AI tooling used to co-author this PR? <!-- If generative AI tooling has been used in the process of authoring this PR, please change below checkbox to `[X]` followed by the name of the tool, uncomment the "Generated-by". --> - [X] Yes - Claude Code <!-- Generated-by: [Tool Name] following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) --> --- * Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)** for more information. Note: commit author/co-author name and email in commits become permanently public when merged. * For fundamental code changes, an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals)) is needed. * When adding dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). * For significant user-facing changes create newsfragment: `{pr_number}.significant.rst`, in [airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments). You can add this file in a follow-up commit after the PR is created so you know the PR number. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
