This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 3 failed / 258 succeeded
Started2020-01-30 22:56
Elapsed1h43m
Revisionmaster
links{u'resultstore': {u'url': u'https://source.cloud.google.com/results/invocations/da4b2239-af84-460e-afe5-0e1aa164de6c/targets/test'}}
resultstorehttps://source.cloud.google.com/results/invocations/da4b2239-af84-460e-afe5-0e1aa164de6c/targets/test
job-versionv1.18.0-alpha.2.262+73409068cd3591
master_os_imagecos-77-12371-114-0
node_os_imagecos-77-12371-114-0
revisionv1.18.0-alpha.2.262+73409068cd3591

Test Failures


1h10m

error during /home/prow/go/src/k8s.io/windows-testing/gce/run-e2e.sh --ginkgo.focus=\[Conformance\]|\[NodeConformance\]|\[sig-windows\] --ginkgo.skip=\[LinuxOnly\]|\[Serial\]|\[Feature:.+\] --minStartupPods=8 --node-os-distro=windows: exit status 1
				from junit_runner.xml

Filter through log files


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

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\]$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:702
Jan 30 23:40:29.093: Timed out after 60.051s.
Expected
    <*errors.errorString | 0xc001c2e630>: {
        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:2020-01-30 23:39:42 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2020-01-30 23:39:42 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [bin-false372c101b-6e68-4ec2-97b5-238baf0ca534]} {Type:ContainersReady Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2020-01-30 23:39:42 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [bin-false372c101b-6e68-4ec2-97b5-238baf0ca534]} {Type:PodScheduled Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2020-01-30 23:39:29 +0000 UTC Reason: Message:}] Message: Reason: NominatedNodeName: HostIP:10.40.0.3 PodIP: PodIPs:[] StartTime:2020-01-30 23:39:42 +0000 UTC InitContainerStatuses:[] ContainerStatuses:[{Name:bin-false372c101b-6e68-4ec2-97b5-238baf0ca534 State:{Waiting:&ContainerStateWaiting{Reason:ContainerCreating,Message:,} Running:nil Terminated:nil} LastTerminationState:{Waiting:nil Running:nil Terminated:nil} Ready:false RestartCount:0 Image:e2eteam/busybox:1.29 ImageID: ContainerID: Started:0xc00083c4a9}] QOSClass:BestEffort EphemeralContainerStatuses:[]}",
    }
to be nil
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/kubelet.go:124
				
				Click to see stdout/stderrfrom junit_05.xml

Find status mentions in log files


Kubernetes e2e suite [sig-windows] Services should be able to create a functioning NodePort service for Windows 2m20s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-windows\]\sServices\sshould\sbe\sable\sto\screate\sa\sfunctioning\sNodePort\sservice\sfor\sWindows$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/windows/service.go:42
Jan 30 23:34:21.932: Unexpected error:
    <*errors.errorString | 0xc001b82090>: {
        s: "failed waiting for pods to be running: timeout waiting for 1 pods to be ready",
    }
    failed waiting for pods to be running: timeout waiting for 1 pods to be ready
occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/windows/service.go:60
				
				Click to see stdout/stderrfrom junit_07.xml

Filter through log files


Show 258 Passed Tests

Show 4595 Skipped Tests