-
Notifications
You must be signed in to change notification settings - Fork 260
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
Restructure PodsReadyTimeout integration tests with short timeout. #2329
Restructure PodsReadyTimeout integration tests with short timeout. #2329
Conversation
Skipping CI for Draft Pull Request. |
✅ Deploy Preview for kubernetes-sigs-kueue canceled.
|
/test all |
/assign @trasc |
3be0921
to
d687d09
Compare
d687d09
to
b97107a
Compare
Integration passed 1/5 /test pull-kueue-test-integration-main |
Integration passed 2/5 /test pull-kueue-test-integration-main |
Integration passed 3/5 /test pull-kueue-test-integration-main |
Integration passed 4/5 /test pull-kueue-test-integration-main |
Integration passed 5/5 /test pull-kueue-test-integration-main |
/ok-to-test |
/cc @IrvingMg @vladikkuzn |
// We assume that the test will get to this check before the timeout expires and the | ||
// kueue cancels the admission. Mentioning this in case this test flakes in the future. | ||
gomega.Eventually(func() bool { |
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 wouldn't think that 10ms for this in general.
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.
This is the type of thing that might flake 1/100 times, which is still distracting.
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.
Yeah, I checked a lot and it worked fine. Moved to "Short PodsReady timeout" to be sure.
@@ -628,9 +663,9 @@ var _ = ginkgo.Describe("SchedulerWithWaitForPodsReadyNonblockingMode", func() { | |||
}) | |||
}) | |||
|
|||
var _ = ginkgo.Context("Short PodsReady timeout", func() { | |||
var _ = ginkgo.Context("Tiny PodsReady timeout", func() { |
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.
Don't we have another context for this already?
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.
For NonblockingMode no.
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
LGTM label has been added. Git tree hash: a0436d2f41a7b48845a733fa3554dc212ca29485
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alculquicondor, mbobrovskyi 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 |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
We should use a shorter timeout (10ms) for the test cases with a single or second reconciliation and should keep using a 1s for test cases with 3 reconciliations.
Which issue(s) this PR fixes:
Fixes #2285
Special notes for your reviewer:
Does this PR introduce a user-facing change?