Dev-iL opened a new pull request, #63918: URL: https://github.com/apache/airflow/pull/63918
related: https://github.com/apache/airflow/pull/63793, https://github.com/apache/airflow/pull/63870 ## Summary - Skip Breeze provider test runs before Docker startup when every selected test path is excluded or suspended for the current Python version. - Preserve explicit pytest path runs such as `test_type="None"` so the earlier skip regression does not come back. ## Details `#63793` fixed one failure mode for Python-version-excluded providers by skipping when pytest ended up with no test directories. `#63870` then reverted that broader filtering because it also skipped valid `test_type="None"` runs where users passed explicit test paths. This change keeps the skip, but moves the decision earlier and makes it specific to provider exclusion data. A new `are_all_test_paths_excluded()` helper checks the test directories implied by the selected provider test type against the excluded and suspended provider sets. When every generated path is excluded for the current Python version, `_run_test` now returns a skip result immediately, before any Docker cleanup or `docker compose run` calls. Because the new check only applies to generated provider test paths, explicit pytest path invocations still run normally. The added Breeze tests cover the full-exclusion skip path, the partial-exclusion path, and the `test_type="None"` regression case from `#63870`. <!-- 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 --> --- ##### 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]
