Commit 2e4e9323 authored by Kubernetes Submit Queue's avatar Kubernetes Submit Queue Committed by GitHub

Merge pull request #36413 from Random-Liu/extend-node-e2e-timeout

Automatic merge from submit-queue Node E2E: Extend the default ci node e2e test timeout to 1h. With more and more test added into node e2e, 45m seems to be not enough now. I saw sometimes the test takes 40+m: * https://storage.googleapis.com/kubernetes-jenkins/logs/kubelet-gce-e2e-ci/10942/build-log.txt (44m4.917870119s) * https://storage.googleapis.com/kubernetes-jenkins/logs/kubelet-gce-e2e-ci/10965/build-log.txt (40m2.37254827s) And sometimes even timeout: * https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubelet-gce-e2e-ci/10968 * https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubelet-gce-e2e-ci/10941 Although it's quite likely that the timeout happened because the limit is too tight, we are not 100% sure. This PR extends the test timeout of regular ci node e2e test to 1h. Let's see whether the timeout will happen again. @yujuhong
parents 31fbb771 0247626e
......@@ -6,3 +6,4 @@ CLEANUP=true
GINKGO_FLAGS='--skip="\[Flaky\]|\[Serial\]"'
SETUP_NODE=false
TEST_ARGS='--enable-cri=true --experimental-mounter-path="" --experimental-mounter-rootfs-path="" --feature-gates="StreamingProxyRedirects=true"'
TIMEOUT=1h
......@@ -15,3 +15,4 @@ GCE_INSTANCE_METADATA="user-data<${GCI_CLOUD_INIT},gci-docker-version=${DOCKER_V
CLEANUP=true
GINKGO_FLAGS='--skip="\[Flaky\]|\[Serial\]"'
SETUP_NODE=true
TIMEOUT=1h
......@@ -6,3 +6,4 @@ CLEANUP=true
GINKGO_FLAGS='--skip="\[Flaky\]|\[Serial\]"'
SETUP_NODE=false
TEST_ARGS=--cgroups-per-qos=true
TIMEOUT=1h
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment