-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
fix(agent): no more requeue when the node succeeded #10681
fix(agent): no more requeue when the node succeeded #10681
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for this fix. How would you go about testing it? Unit tests?
ok~ |
0489744
to
b7325a3
Compare
done~ PTAL, thx @alexec |
Signed-off-by: scott <scottwangsxll@gmail.com>
b7325a3
to
380d370
Compare
@@ -368,6 +368,9 @@ func (ae *AgentExecutor) executePluginTemplate(ctx context.Context, tmpl wfv1.Te | |||
return 0, err | |||
} else if reply.Node != nil { | |||
*result = *reply.Node | |||
if reply.Node.Phase == wfv1.NodeSucceeded { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this include failed and errored nodes?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think so. Because in failure, the user needs to explicitly give
the delay of the requeue.
Signed-off-by: scott <scottwangsxll@gmail.com> Signed-off-by: Elifarley <elifarley@gmail.com>
Signed-off-by: scott <scottwangsxll@gmail.com>
Fixes: As the title