This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 3 failed / 192 succeeded
Started2020-02-17 08:01
Elapsed4h28m
Revision
Buildergke-prow-default-pool-cf4891d4-0mh6
links{u'resultstore': {u'url': u'https://source.cloud.google.com/results/invocations/ae7fb8eb-2687-4f87-a421-2b03d60b4ff0/targets/test'}}
pod99d8167c-515b-11ea-9bea-16a0f55e352c
resultstorehttps://source.cloud.google.com/results/invocations/ae7fb8eb-2687-4f87-a421-2b03d60b4ff0/targets/test
infra-commitf5dd3ee0e
job-versionv1.17.4-beta.0.1+aa9a28326e8075
master_os_imagecos-77-12371-89-0
node_os_imagecos-77-12371-89-0
pod99d8167c-515b-11ea-9bea-16a0f55e352c
revisionv1.17.4-beta.0.1+aa9a28326e8075

Test Failures


Kubernetes e2e suite [sig-scheduling] SchedulerPredicates [Serial] validates MaxPods limit number of pods that are allowed to run [Slow] 4m36s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-scheduling\]\sSchedulerPredicates\s\[Serial\]\svalidates\sMaxPods\slimit\snumber\sof\spods\sthat\sare\sallowed\sto\srun\s\[Slow\]$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/predicates.go:122
Feb 17 08:27:02.583: Unexpected error:
    <*errors.errorString | 0xc0000d5950>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/predicates.go:749
				
				Click to see stdout/stderrfrom junit_01.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: gce-localssd-scsi-fs] [Serial] [Testpattern: Pre-provisioned PV (filesystem volmode)] disruptive[Disruptive] Should test that pv written before kubelet restart is readable after restart. 1.66s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sIn\-tree\sVolumes\s\[Driver\:\slocal\]\[LocalVolumeType\:\sgce\-localssd\-scsi\-fs\]\s\[Serial\]\s\[Testpattern\:\sPre\-provisioned\sPV\s\(filesystem\svolmode\)\]\sdisruptive\[Disruptive\]\sShould\stest\sthat\spv\swritten\sbefore\skubelet\srestart\sis\sreadable\safter\srestart\.$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/disruptive.go:149
Feb 17 08:27:05.093: Unexpected error:
    <*errors.errorString | 0xc0004560d0>: {
        s: "pod ran to completion",
    }
    pod ran to completion
occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/utils/host_exec.go:103
				
				Click to see stdout/stderrfrom junit_01.xml

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


Test 4h10m

error during ./hack/ginkgo-e2e.sh --ginkgo.focus=\[Serial\]|\[Disruptive\] --ginkgo.skip=\[Flaky\]|\[Feature:.+\] --minStartupPods=8 --report-dir=/workspace/_artifacts --disable-log-dump=true: exit status 1
				from junit_runner.xml

Filter through log files | View test history on testgrid


Show 192 Passed Tests

Show 4666 Skipped Tests