choo121600 opened a new pull request, #64540:
URL: https://github.com/apache/airflow/pull/64540
<!-- SPDX-License-Identifier: Apache-2.0
https://www.apache.org/licenses/LICENSE-2.0 -->
## Why
* Tests starting before Dags are parsed → API calls intermittently return
404 or stale state.
* Cleanup failing on running Dag runs (409) or timing out under CI load,
leaving residual state that affects subsequent tests.
## Change
* **Pre-warm Dags in global setup**: Explicitly wait until all test Dags are
present in the DagBag before Playwright workers start. This eliminates race
conditions where tests begin before the scheduler has registered the Dags.
* **Normalize per-request timeouts to 10s**: Individual API call timeouts in
polling helpers were 30s — unnecessarily long for calls that are retried in
tight loops. Reduced to 10s so failures surface faster while polling still
provides overall tolerance.
* **Harden Dag run cleanup**: `safeCleanupDagRun` now always force-fails the
run before attempting deletion (instead of reacting to 409 conflicts after the
fact), and retries once on timeout. This ensures the API does not block on
active task execution during deletion.
* **Increase expect timeout to 10s**: Assertion timeout raised from 5s to
10s to reduce flaky failures on slower CI environments.
part of: #64024
related: #63036
<!--
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".
-->
- [ ] Yes (please specify the tool below)
<!--
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]
