-
Notifications
You must be signed in to change notification settings - Fork 78
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
Cherry-pick two commits #461
Cherry-pick two commits #461
Conversation
Today, when a WaitTask timeout happens, the WaitTask sends the TimeoutError on the TaskChannel. After receiving the TimeoutError, `baseRunner.run` terminates immediately by returning the error to its caller (Applier.Run or Destroyer.Run). The caller then sends the error onto the EventChannel and terminates. With this PR, when a WaitTask timeout happens, the WaitTask sends a WaitType Event including the TimeoutError on the EventChannel, and then sends an empty TaskResult on the TaskChannel. An empty TaskResult suggests that the task finished successfully, and therefore `baseRunner.run` would continue instead of terminate. The motivation of this change is to make sure that cli-utils only terminates on fatal errors (such as inventory-related errors, and ApplyOptions creation errors). A WaitTask timeout may not always mean a fatal error (it may happen because the StatusPoller has not finished polling everything, or some but not all the resources have not reached the desired status), and therefore should not terminate cli-utils.
/cc @mortent |
/test ? |
@haiyanmeng: No presubmit jobs available for kubernetes-sigs/cli-utils@release-0.26 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. |
/test all |
@haiyanmeng: No presubmit jobs available for kubernetes-sigs/cli-utils@release-0.26 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. |
I think you need to run |
Usually best to just run |
/test all |
/approve |
/label tide/merge-method-squash |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: haiyanmeng, mortent, seans3 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
No description provided.