You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here is the example running on 263cb70 (one commit before the offending commit):
Name: steps-dlr2r
Namespace: argo
ServiceAccount: default
Status: Failed
Message: child 'steps-dlr2r-165846992' failed
Created: Fri Oct 18 15:57:50 -0700 (30 seconds ago)
Started: Fri Oct 18 15:57:50 -0700 (30 seconds ago)
Finished: Fri Oct 18 15:58:20 -0700 (now)
Duration: 30 seconds
STEP PODNAME DURATION MESSAGE
✖ steps-dlr2r (hello-hello-hello) child 'steps-dlr2r-165846992' failed
└---✖ hello1 (whalesay) No more retries left
├-✖ hello1(0) (whalesay) steps-dlr2r-3706177139 8s failed with exit code 1
├-✖ hello1(1) (whalesay) steps-dlr2r-15351222 6s failed with exit code 1
├-✖ hello1(2) (whalesay) steps-dlr2r-3907802757 5s failed with exit code 1
└-✖ hello1(3) (whalesay) steps-dlr2r-1559186360 7s failed with exit code 1
Here is the same example running on 30a91ef (the offending commit). The workflow runs to this screen and continues indefinitely until manually stopped:
Builds on or after #1669 (30a91ef) hang the execution when retrying nodes.
Consider this example:
Here is the example running on 263cb70 (one commit before the offending commit):
Here is the same example running on 30a91ef (the offending commit). The workflow runs to this screen and continues indefinitely until manually stopped:
@dtaniwaki ?
@sarabala1979 Unless I'm missing something, this is seems like a major bug and should block our release until it is resolved or reverted.
The text was updated successfully, but these errors were encountered: