amoghrajesh opened a new pull request, #76904:
URL: https://github.com/apache/airflow/pull/76904
<!-- 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:
https://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 (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)
-->
With `repair_run=True`, `DatabricksRunNowOperator` repairs a run that fails
while the task is watching it, rerunning only the failed tasks. When that
repair succeeded, the task still raised the original failure, so Airflow marked
it failed even though the Databricks run finished successfully. A retry would
then start the whole job again.
This affects only the non-deferrable mode. In deferrable mode the repaired
run goes back to the triggerer, so that path already works.
The existing repair test only covered a run that stays failed after the
repair, so this case had no test.
## Testing
Ran against a real Databricks job (`retries=0`, `repair_run=True`), where
the first run fails in its `report` task and the repair succeeds.
**Before:** the repair succeeds, but the task fails.
<img width="3200" height="2000" alt="before_logs"
src="https://github.com/user-attachments/assets/c7345ea9-5f19-4c0a-9e70-f6c220fed731";
/>
**After:** the repair succeeds, and the task succeeds.
<img width="3200" height="2000" alt="after_logs"
src="https://github.com/user-attachments/assets/4a3728d9-9ec1-4011-9ea4-8bfdaf456b10";
/>
---
* 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]
