Fix misleading log message in task_runner clear_on_success block#67836
Merged
amoghrajesh merged 2 commits intoJun 1, 2026
Conversation
kaxil
reviewed
Jun 1, 2026
kaxil
approved these changes
Jun 1, 2026
Co-authored-by: Kaxil Naik <kaxilnaik@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Was generative AI tooling used to co-author this PR?
Raised by @kaxil on PR #66859 post review comment.
The logs mention that "Task state will be cleared by the server because clear_on_success is enabled."
But
_clear_backend_only()is called immediately after on the worker side, the backend(e.g. custom S3 store) is cleared here, not by the server. Only the DB rows are cleared by
the server.
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.