-
Notifications
You must be signed in to change notification settings - Fork 4.8k
AUTH-428: add PSa labelsyncer managed labels e2e tests #28257
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
base: main
Are you sure you want to change the base?
Conversation
|
@liouk: This pull request references AUTH-428 which is a valid jira 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. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: liouk The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
cb80df0 to
49d0add
Compare
49d0add to
776c4bb
Compare
|
/retest |
|
/retest-required |
| } | ||
|
|
||
| func waitAndGetNamespace(ctx context.Context, oc *exutil.CLI, nsName string) (*corev1.Namespace, error) { | ||
| time.Sleep(2 * time.Second) |
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.
Wait until something happens is always better.
A hardcoded timelimit is always the worst case. It can also introduce a spiral of longer and longer test durations. If the cluster is slow, it will cause flakiness, which will then lead to an increase of the static sleep in all cases.
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.
I've added a generic polling function that waits for the namespace object to be updated by the labelsyncer after the original create/update, in 9418921.
I chose a generic equality condition, as what the labelsyncer is expected to do varies per test and test case (and in some cases no change is expected at all).
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.
A polling function is a great idea.
Test frameworks that offer a "wait" function are doing exactly that.
|
added review fixes as fixups for clarity; will squash once reviewed |
|
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
|
/remove-lifecycle stale |
|
/retest |
9418921 to
2649633
Compare
|
/retest |
2649633 to
b0021c5
Compare
|
/hold cancel |
|
/retest |
|
/hold |
20e5af0 to
5486b12
Compare
5486b12 to
ea0c6cd
Compare
|
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
|
/remove-lifecycle stale |
|
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
|
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
|
/remove-lifecycle rotten |
|
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
|
/remove-lifecycle stale |
|
Risk analysis has seen new tests most likely introduced by this PR. New Test Risks for sha: ea0c6cd
New tests seen in this PR at sha: ea0c6cd
|
|
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
|
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
|
/remove-lifecycle rotten |
|
PR needs rebase. 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-sigs/prow repository. |
|
@liouk: The following tests failed, say
Full PR test history. Your PR dashboard. 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-sigs/prow repository. I understand the commands that are listed here. |
Adds e2e tests for the behavior added here: