-
Notifications
You must be signed in to change notification settings - Fork 1.2k
🏃 (:running:, other) Try to stabilize the flaky process_test #777
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
🏃 (:running:, other) Try to stabilize the flaky process_test #777
Conversation
/retest |
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.
/lgtm
/assign @gerred
I would also try to see if we need to assign more resources to our prow jobs, like CPU and memory. We've done this for Cluster API and it has worked nicely. I can take a look later.
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.
/lgtm
/approve |
@gerred can you please re-approve? |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alenkacz, gerred 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 |
The test is flaky, see https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_controller-runtime/592/pull-controller-runtime-test-master/1220082018474266624 or https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_controller-runtime/776/pull-controller-runtime-test-master/1220286274334625792
My hunch was that 20 millis is not enoughso I tried fixing the test by using much bigger poll interval.