-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[TEP-0121]: Cleanup existing test cases that check TaskRuns and Runs status with consideration of Retries
#6662
Comments
Issues go stale after 90d of inactivity. /lifecycle stale Send feedback to tektoncd/plumbing. |
Stale issues rot after 30d of inactivity. /lifecycle rotten Send feedback to tektoncd/plumbing. |
Rotten issues close after 30d of inactivity. /close Send feedback to tektoncd/plumbing. |
@tekton-robot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
TEP-0121 proposes to improves
Retries
behavior, we stopped relying onlen(tr.status.retriesStatus)
to determine whether a TaskRun has finished retries / not, instead, we turns to only rely onConditionSucceeded
. That's said, the remainingRetries
is irrelevant to the current status of aTaskRun
/CustomRun
.This issue originates from #6661 (comment).
The text was updated successfully, but these errors were encountered: