Uh oh!
There was an error while loading. Please reload this page.
avoid retrying after KubernetesPodOperator has been marked as failed - #36749
Conversation
a7573f7 to
6b0f18fCompare
dirrao
left a comment
There was a problem hiding this comment.
Nice Work. It would be great if possible then, add the test cases.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
4f3b55b to
141b7a8CompareUh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
141b7a8 to
c10f762Compare
amoghrajesh
left a comment
There was a problem hiding this comment.
Looks good to me! Pending comments from @dirrao.
@hussein-awala WDYT?
Uh oh!
There was an error while loading. Please reload this page.
jedcunningham
left a comment
There was a problem hiding this comment.
We should also add some test coverage to make sure we don't accidentally reintroduce this.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
b3eeab9 to
1eeeb3eCompare1eeeb3e to
a7f25edCompareUh oh!
There was an error while loading. Please reload this page.
jedcunningham
left a comment
There was a problem hiding this comment.
On second though, I think we are okay without test coverage on this. LGTM.
Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com>
if the task has been killed, do not cleanup again
f7f9935 to
ca60adcCompare
After marking the task as failed, KPO still has a
finallysection to run, which causes #36471. In this PR, I tried to check whetheron_killedis called and do not raise exception in thefinallysection as it'll overwrite the "Mark as failed" behavior^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.