Dev-iL opened a new pull request, #63793:
URL: https://github.com/apache/airflow/pull/63793
## Summary
- Fix provider test runner to skip gracefully when all test directories are
excluded for the current Python version.
- Fix PROD image docker tests to read `provider.yaml` exclusions and filter
expected providers/imports based on the image's Python version.
## Details
### Skip provider tests when all test directories are excluded
When running provider test suites (e.g., `Providers[google]`) on a Python
version where that provider is excluded, `generate_args_for_pytest` removes the
test folders upstream. However, the skip check in `_run_test` only triggered
when the `--ignore` filter itself removed something. Since folders were already
gone, the guard condition was never met, leaving pytest with only flags and no
test directories — causing it to crash on unrecognized custom arguments.
The fix removes the overly strict guard so the skip fires whenever no test
directories remain in the args.
### Fix PROD image docker tests for excluded providers
The docker tests expected all providers from
`prod_image_installed_providers.txt` to be present, but providers like google
and amazon may declare `excluded-python-versions` in their `provider.yaml`. The
tests now read these exclusions and filter expected providers and imports based
on the Docker image's Python version.
<!-- 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.
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
-->
related: #63520
---
##### 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 (please specify the tool below)
Generated-by: Claude Opus 4.6 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]
