This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 2 failed / 16 succeeded
Started2020-01-31 12:01
Elapsed1h47m
Revision
Buildergke-prow-default-pool-cf4891d4-l6s3
links{u'resultstore': {u'url': u'https://source.cloud.google.com/results/invocations/6ed66def-84dc-4aab-b335-62c9b93e0be9/targets/test'}}
pod4ad3166e-4421-11ea-bb35-aec66a26cefa
resultstorehttps://source.cloud.google.com/results/invocations/6ed66def-84dc-4aab-b335-62c9b93e0be9/targets/test
infra-commit0997840da
job-versionv1.16.7-beta.0.1+8fc866b3067974
pod4ad3166e-4421-11ea-bb35-aec66a26cefa
repok8s.io/kubernetes
repo-commita1e6da402568572f56e7605c0091f3e57009eb20
repos{u'k8s.io/kubernetes': u'release-1.16', u'k8s.io/perf-tests': u'release-1.16'}
revisionv1.16.7-beta.0.1+8fc866b3067974

Test Failures


ClusterLoaderV2 1h8m

error during /go/src/k8s.io/perf-tests/run-e2e.sh cluster-loader2 --nodes=100 --prometheus-scrape-node-exporter --provider=gce --report-dir=/workspace/_artifacts --testconfig=testing/density/config.yaml --testconfig=testing/load/config.yaml --testoverrides=./testing/chaosmonkey/override.yaml --testoverrides=./testing/load/gce/throughput_override.yaml: exit status 1
				from junit_runner.xml

Filter through log files | View test history on testgrid


ClusterLoaderV2 testing/density/config.yaml 37m3s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=ClusterLoaderV2\stesting\/density\/config\.yaml$'
:0
[measurement call PodStartupLatency - SaturationPodStartupLatency error: pod startup: too high latency 90th percentile: got 6m18.314157276s expected: 5m30s
measurement call WaitForControlledPodsRunning - WaitForRunningLatencyDeployments error: 78 objects timed out: Deployments: test-ysm4ql-1/latency-deployment-85, test-ysm4ql-1/latency-deployment-79, test-ysm4ql-1/latency-deployment-8, test-ysm4ql-1/latency-deployment-132, test-ysm4ql-1/latency-deployment-65, test-ysm4ql-1/latency-deployment-7, test-ysm4ql-1/latency-deployment-42, test-ysm4ql-1/latency-deployment-23, test-ysm4ql-1/latency-deployment-119, test-ysm4ql-1/latency-deployment-74, test-ysm4ql-1/latency-deployment-24, test-ysm4ql-1/latency-deployment-10, test-ysm4ql-1/latency-deployment-135, test-ysm4ql-1/latency-deployment-171, test-ysm4ql-1/latency-deployment-125, test-ysm4ql-1/latency-deployment-16, test-ysm4ql-1/latency-deployment-150, test-ysm4ql-1/latency-deployment-81, test-ysm4ql-1/latency-deployment-161, test-ysm4ql-1/latency-deployment-146, test-ysm4ql-1/latency-deployment-20, test-ysm4ql-1/latency-deployment-144, test-ysm4ql-1/latency-deployment-122, test-ysm4ql-1/latency-deployment-84, test-ysm4ql-1/latency-deployment-163, test-ysm4ql-1/latency-deployment-168, test-ysm4ql-1/latency-deployment-68, test-ysm4ql-1/latency-deployment-149, test-ysm4ql-1/latency-deployment-128, test-ysm4ql-1/latency-deployment-67, test-ysm4ql-1/latency-deployment-123, test-ysm4ql-1/latency-deployment-83, test-ysm4ql-1/latency-deployment-133, test-ysm4ql-1/latency-deployment-162, test-ysm4ql-1/latency-deployment-169, test-ysm4ql-1/latency-deployment-115, test-ysm4ql-1/latency-deployment-118, test-ysm4ql-1/latency-deployment-30, test-ysm4ql-1/latency-deployment-22, test-ysm4ql-1/latency-deployment-72, test-ysm4ql-1/latency-deployment-26, test-ysm4ql-1/latency-deployment-166, test-ysm4ql-1/latency-deployment-87, test-ysm4ql-1/latency-deployment-25, test-ysm4ql-1/latency-deployment-127, test-ysm4ql-1/latency-deployment-131, test-ysm4ql-1/latency-deployment-167, test-ysm4ql-1/latency-deployment-27, test-ysm4ql-1/latency-deployment-88, test-ysm4ql-1/latency-deployment-147, test-ysm4ql-1/latency-deployment-129, test-ysm4ql-1/latency-deployment-165, test-ysm4ql-1/latency-deployment-112, test-ysm4ql-1/latency-deployment-145, test-ysm4ql-1/latency-deployment-28, test-ysm4ql-1/latency-deployment-31, test-ysm4ql-1/latency-deployment-13, test-ysm4ql-1/latency-deployment-82, test-ysm4ql-1/latency-deployment-138, test-ysm4ql-1/latency-deployment-124, test-ysm4ql-1/latency-deployment-134, test-ysm4ql-1/latency-deployment-89, test-ysm4ql-1/latency-deployment-120, test-ysm4ql-1/latency-deployment-29, test-ysm4ql-1/latency-deployment-104, test-ysm4ql-1/latency-deployment-159, test-ysm4ql-1/latency-deployment-164, test-ysm4ql-1/latency-deployment-130, test-ysm4ql-1/latency-deployment-148, test-ysm4ql-1/latency-deployment-136, test-ysm4ql-1/latency-deployment-137, test-ysm4ql-1/latency-deployment-142, test-ysm4ql-1/latency-deployment-71, test-ysm4ql-1/latency-deployment-126, test-ysm4ql-1/latency-deployment-19, test-ysm4ql-1/latency-deployment-86, test-ysm4ql-1/latency-deployment-15, test-ysm4ql-1/latency-deployment-121
measurement call PodStartupLatency - PodStartupLatency error: pod startup: too high latency 90th percentile: got 2m44.254009799s expected: 5s]
:0
				from junit.xml

Find startup mentions in log files | View test history on testgrid


Show 16 Passed Tests