-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Stabilize ingressip controller unit test #20352
Stabilize ingressip controller unit test #20352
Conversation
Eliminate flakes in the TestBasicControllerFlow test by polling fake action state rather than relying on custom fake watch consumption; the event counts on the watch are not deterministic, and so the previous assumption of two events doesn't always hold and causes a deadlock in the test's custom controller handler. Refactor the test to remove unnecessary fake watch and controller setup; just use the fake client and its built-in watch capabilities directly.
On master I can reproduce the flake with |
10k runs and no failures, so I think this is good assuming the assertions are valid (previously there weren't really any) |
/retest |
1 similar comment
/retest |
/test gcp |
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
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ironcladlou, pravisankar 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 |
/test gcp |
Eliminate flakes in the TestBasicControllerFlow test by polling fake action
state rather than relying on custom fake watch consumption; the event counts on
the watch are not deterministic, and so the previous assumption of two events
doesn't always hold and causes a deadlock in the test's custom controller
handler.
Refactor the test to remove unnecessary fake watch and controller setup; just
use the fake client and its built-in watch capabilities directly.
Add stronger update validity assertions.
/xref #20168
/xref this flake
/cc @openshift/sig-network-edge
/cc @smarterclayton