This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultSUCCESS
Tests 1 failed / 272 succeeded
Started2019-11-13 07:35
Elapsed43m37s
Revision
Buildergke-prow-ssd-pool-1a225945-lf79
links{u'resultstore': {u'url': u'https://source.cloud.google.com/results/invocations/2a633b9c-9c66-4545-949b-84c81a9840b1/targets/test'}}
podfb1e2075-05e7-11ea-993c-5ac2047d9356
resultstorehttps://source.cloud.google.com/results/invocations/2a633b9c-9c66-4545-949b-84c81a9840b1/targets/test
infra-commitcce53531b
job-versionv1.16.3-beta.0.56+b3cbbae08ec52a-dirty
podfb1e2075-05e7-11ea-993c-5ac2047d9356
repok8s.io/kubernetes
repo-commitb3cbbae08ec52a7fc73d334838e18d17e8512749
repos{u'k8s.io/kubernetes': u'release-1.16', u'sigs.k8s.io/cloud-provider-azure': u'master'}
revisionv1.16.3-beta.0.56+b3cbbae08ec52a-dirty

Test Failures


Kubernetes e2e suite [k8s.io] Kubelet when scheduling a busybox command that always fails in a pod should have an terminated reason [NodeConformance] [Conformance] 1m10s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[k8s\.io\]\sKubelet\swhen\sscheduling\sa\sbusybox\scommand\sthat\salways\sfails\sin\sa\spod\sshould\shave\san\sterminated\sreason\s\[NodeConformance\]\s\[Conformance\]$'
test/e2e/framework/framework.go:698
Nov 13 08:03:14.934: Timed out after 60.000s.
Expected
    <*errors.errorString | 0xc0022ca1f0>: {
        s: "expected state to be terminated. Got pod status: {Phase:Pending Conditions:[{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2019-11-13 08:02:19 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2019-11-13 08:02:19 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [bin-false4307f934-5942-4d93-950b-cbcff1c1fc0d]} {Type:ContainersReady Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2019-11-13 08:02:19 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [bin-false4307f934-5942-4d93-950b-cbcff1c1fc0d]} {Type:PodScheduled Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2019-11-13 08:02:14 +0000 UTC Reason: Message:}] Message: Reason: NominatedNodeName: HostIP:10.240.0.4 PodIP: PodIPs:[] StartTime:2019-11-13 08:02:19 +0000 UTC InitContainerStatuses:[] ContainerStatuses:[{Name:bin-false4307f934-5942-4d93-950b-cbcff1c1fc0d State:{Waiting:&ContainerStateWaiting{Reason:ContainerCreating,Message:,} Running:nil Terminated:nil} LastTerminationState:{Waiting:nil Running:nil Terminated:nil} Ready:false RestartCount:0 Image:docker.io/library/busybox:1.29 ImageID: ContainerID: Started:0xc00298211a}] QOSClass:BestEffort EphemeralContainerStatuses:[]}",
    }
to be nil
test/e2e/common/kubelet.go:123
				
				Click to see stdout/stderrfrom junit_01.xml

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


Show 272 Passed Tests

Show 4473 Skipped Tests