OCPBUGS-2429: Fix TestReloadInterval min value test cases and race conditions#842
Conversation
|
@gcs278: This pull request references Jira Issue OCPBUGS-2429, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn 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. |
52f66f6 to
86372aa
Compare
|
/refresh jira |
645b694 to
b983acc
Compare
|
/jira refresh |
|
@gcs278: This pull request references Jira Issue OCPBUGS-2429, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
Requesting review from QA contact: DetailsIn 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. |
b983acc to
3ee9c29
Compare
fix race condition in which it passes as a false positive by forcing the ingress operator to recreated the router deployment instead of waiting on the ingress operator to report Available. - test/e2e/reloadinterval_test.go: Add deletion of router deployment to trigger reconcile and fix min value test cases
3ee9c29 to
08803d1
Compare
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Miciah The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest-required |
| {"set reloadInterval 5us", metav1.Duration{Duration: 5 * time.Microsecond}, "5s", true}, | ||
| {"set reloadInterval 500ms", metav1.Duration{Duration: 500 * time.Millisecond}, "5s", true}, | ||
| {"set reloadInterval 200ns", metav1.Duration{Duration: 200 * time.Nanosecond}, "1s", true}, | ||
| {"set reloadInterval 5us", metav1.Duration{Duration: 5 * time.Microsecond}, "1s", true}, |
There was a problem hiding this comment.
does setting to 1s really help ? Won't it cause load on the router ?
There was a problem hiding this comment.
Not exactly - it's the value the test is looking for in the router deployment ENV variable. So no load affects, just a comparison value that was wrong.
|
The PR looks lgtm so /lgtm |
|
/lgtm |
|
@gcs278: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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 understand the commands that are listed here. |
|
@gcs278: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-2429 has been moved to the MODIFIED state. DetailsIn 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. |
|
/label qe-approve |
|
@ShudiLi: The label(s) DetailsIn 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. |
|
cancel /label qe-approve |
OCPBUGS-2429: Fix TestReloadInterval min value test cases to 1s and fix race condition in which it passes as a false positive by forcing the ingress operator to recreated the router deployment instead of waiting on the ingress operator to report Available.
test/e2e/reloadinterval_test.go: Add deletion of router deployment to trigger reconcile and fix min value test cases