-
Notifications
You must be signed in to change notification settings - Fork 674
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] subworkflow timeout propagation #4766
Merged
Merged
Conversation
This file contains 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
pvditt
changed the title
Bug/subworkflow timeout propagation
[BUG] subworkflow timeout propagation
Jan 23, 2024
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #4766 +/- ##
==========================================
- Coverage 58.21% 58.20% -0.01%
==========================================
Files 626 626
Lines 53855 53911 +56
==========================================
+ Hits 31349 31377 +28
- Misses 19996 20023 +27
- Partials 2510 2511 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
dosubot
bot
added
the
size:S
This PR changes 10-29 lines, ignoring generated files.
label
Jan 23, 2024
hamersaw
reviewed
Jan 24, 2024
Signed-off-by: Paul Dittamo <[email protected]>
Signed-off-by: Paul Dittamo <[email protected]>
Signed-off-by: Paul Dittamo <[email protected]>
This reverts commit 1172ef6. Signed-off-by: Paul Dittamo <[email protected]>
…g node execution events Signed-off-by: Paul Dittamo <[email protected]>
pvditt
force-pushed
the
bug/subworkflow-timeout-propagation
branch
from
January 24, 2024 07:19
0037b29
to
f011b15
Compare
hamersaw
approved these changes
Jan 24, 2024
This was referenced Jan 24, 2024
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.
Tracking issue
#4087
#4765
Why are the changes needed?
When a subworkflow's task fails due to reaching node-active-deadline, the workflow does not fail. The workflow continues to run after the timed out task gets aborted and getting set to "UNKNOWN" state
When a task time's out due to reaching node-active-deadline, the task's status gets set to "UNKNOWN"
What changes were proposed in this pull request?
Have subworkflows handle TimedOut state
Transform EPhaseTimedout -> NodeExecution_TIMED_OUT when creating node execution events
How was this patch tested?
Ran a couple workflows. Would be a decent effort to add unit testing - can add if needed.
Setup process
Test subworkflow timeout propagation (will hit node-active-deadline on retry)
To isolate test to persisting aborted node on TimeOut:
Set node-active-deadline to small value in Flyte config:
Screenshots
Check all the applicable boxes
Related PRs
Docs link