Use shorter timeout if possible.
- Add PodStartShortTimeout and ClaimProvisionShortTimeout constants. - Change framework.PodStartTimeout to framework.PodStartShortTimeout in persistent_volumes-local.go. Busybox image is very small, no need to wait for a long time.
This commit is contained in:
@@ -113,6 +113,11 @@ const (
|
||||
// TODO: Make this 30 seconds once #4566 is resolved.
|
||||
PodStartTimeout = 5 * time.Minute
|
||||
|
||||
// Same as `PodStartTimeout` to wait for the pod to be started, but shorter.
|
||||
// Use it case by case when we are sure pod start will not be delayed
|
||||
// minutes by slow docker pulls or something else.
|
||||
PodStartShortTimeout = 1 * time.Minute
|
||||
|
||||
// If there are any orphaned namespaces to clean up, this test is running
|
||||
// on a long lived cluster. A long wait here is preferably to spurious test
|
||||
// failures caused by leaked resources from a previous test run.
|
||||
@@ -156,6 +161,10 @@ const (
|
||||
// How long claims have to become dynamically provisioned
|
||||
ClaimProvisionTimeout = 5 * time.Minute
|
||||
|
||||
// Same as `ClaimProvisionTimeout` to wait for claim to be dynamically provisioned, but shorter.
|
||||
// Use it case by case when we are sure this timeout is enough.
|
||||
ClaimProvisionShortTimeout = 1 * time.Minute
|
||||
|
||||
// How long claims have to become bound
|
||||
ClaimBindingTimeout = 3 * time.Minute
|
||||
|
||||
|
||||
Reference in New Issue
Block a user