This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 8 failed / 307 succeeded
Started2021-10-09 05:15
Elapsed58m21s
Revisionmaster
job-versionv1.23.0-alpha.3.249+80056f73a614b2
kubetest-version
revisionv1.23.0-alpha.3.249+80056f73a614b2

Test Failures


Kubernetes e2e suite [sig-node] Container Runtime blackbox test on terminated container should report termination message from file when pod succeeds and TerminationMessagePolicy FallbackToLogsOnError is set [Excluded:WindowsDocker] [NodeConformance] [Conformance] 10s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-node\]\sContainer\sRuntime\sblackbox\stest\son\sterminated\scontainer\sshould\sreport\stermination\smessage\sfrom\sfile\swhen\spod\ssucceeds\sand\sTerminationMessagePolicy\sFallbackToLogsOnError\sis\sset\s\[Excluded\:WindowsDocker\]\s\[NodeConformance\]\s\[Conformance\]$'
/home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
Oct  9 05:52:42.129: Expected
    <string>: 
to equal
    <string>: OK
/home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/common/node/runtime.go:165
				
				Click to see stdout/stderrfrom junit_01.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-node] Container Runtime blackbox test on terminated container should report termination message if TerminationMessagePath is set [Excluded:WindowsDocker] [NodeConformance] 5m1s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-node\]\sContainer\sRuntime\sblackbox\stest\son\sterminated\scontainer\sshould\sreport\stermination\smessage\sif\sTerminationMessagePath\sis\sset\s\[Excluded\:WindowsDocker\]\s\[NodeConformance\]$'
/home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/common/node/runtime.go:171
Oct  9 05:37:38.716: Timed out after 300.001s.
Expected
    <v1.PodPhase>: Failed
to equal
    <v1.PodPhase>: Succeeded
/home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/common/node/runtime.go:154
				
				Click to see stdout/stderrfrom junit_02.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] Subpath Atomic writer volumes should support subpaths with configmap pod [Excluded:WindowsDocker] [Conformance] 5m5s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sSubpath\sAtomic\swriter\svolumes\sshould\ssupport\ssubpaths\swith\sconfigmap\spod\s\[Excluded\:WindowsDocker\]\s\[Conformance\]$'
/home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
Oct  9 05:57:33.733: Unexpected error:
    <*errors.errorString | 0xc003720e40>: {
        s: "expected pod \"pod-subpath-test-configmap-9cqd\" success: Gave up after waiting 5m0s for pod \"pod-subpath-test-configmap-9cqd\" to be \"Succeeded or Failed\"",
    }
    expected pod "pod-subpath-test-configmap-9cqd" success: Gave up after waiting 5m0s for pod "pod-subpath-test-configmap-9cqd" to be "Succeeded or Failed"
occurred
/home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/util.go:743
				
				Click to see stdout/stderrfrom junit_02.xml

Find pod-subpath-test-configmap-9cqd mentions in log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] Subpath Atomic writer volumes should support subpaths with configmap pod with mountPath of existing file [Excluded:WindowsDocker] [Conformance] 5m10s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sSubpath\sAtomic\swriter\svolumes\sshould\ssupport\ssubpaths\swith\sconfigmap\spod\swith\smountPath\sof\sexisting\sfile\s\[Excluded\:WindowsDocker\]\s\[Conformance\]$'
/home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
Oct  9 06:02:44.484: Unexpected error:
    <*errors.errorString | 0xc003486360>: {
        s: "expected pod \"pod-subpath-test-configmap-fslx\" success: Gave up after waiting 5m0s for pod \"pod-subpath-test-configmap-fslx\" to be \"Succeeded or Failed\"",
    }
    expected pod "pod-subpath-test-configmap-fslx" success: Gave up after waiting 5m0s for pod "pod-subpath-test-configmap-fslx" to be "Succeeded or Failed"
occurred
/home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/util.go:743
				
				Click to see stdout/stderrfrom junit_01.xml

Find pod-subpath-test-configmap-fslx mentions in log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] Subpath Atomic writer volumes should support subpaths with downward pod [Excluded:WindowsDocker] [Conformance] 5m5s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sSubpath\sAtomic\swriter\svolumes\sshould\ssupport\ssubpaths\swith\sdownward\spod\s\[Excluded\:WindowsDocker\]\s\[Conformance\]$'
/home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
Oct  9 05:46:20.571: Unexpected error:
    <*errors.errorString | 0xc00468f1f0>: {
        s: "expected pod \"pod-subpath-test-downwardapi-fm62\" success: Gave up after waiting 5m0s for pod \"pod-subpath-test-downwardapi-fm62\" to be \"Succeeded or Failed\"",
    }
    expected pod "pod-subpath-test-downwardapi-fm62" success: Gave up after waiting 5m0s for pod "pod-subpath-test-downwardapi-fm62" to be "Succeeded or Failed"
occurred
/home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/util.go:743
				
				Click to see stdout/stderrfrom junit_04.xml

Find pod-subpath-test-downwardapi-fm62 mentions in log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] Subpath Atomic writer volumes should support subpaths with projected pod [Excluded:WindowsDocker] [Conformance] 5m3s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sSubpath\sAtomic\swriter\svolumes\sshould\ssupport\ssubpaths\swith\sprojected\spod\s\[Excluded\:WindowsDocker\]\s\[Conformance\]$'
/home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
Oct  9 06:05:57.158: Unexpected error:
    <*errors.errorString | 0xc003e29460>: {
        s: "expected pod \"pod-subpath-test-projected-l7t2\" success: Gave up after waiting 5m0s for pod \"pod-subpath-test-projected-l7t2\" to be \"Succeeded or Failed\"",
    }
    expected pod "pod-subpath-test-projected-l7t2" success: Gave up after waiting 5m0s for pod "pod-subpath-test-projected-l7t2" to be "Succeeded or Failed"
occurred
/home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/util.go:743
				
				Click to see stdout/stderrfrom junit_04.xml

Find pod-subpath-test-projected-l7t2 mentions in log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] Subpath Atomic writer volumes should support subpaths with secret pod [Excluded:WindowsDocker] [Conformance] 5m3s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sSubpath\sAtomic\swriter\svolumes\sshould\ssupport\ssubpaths\swith\ssecret\spod\s\[Excluded\:WindowsDocker\]\s\[Conformance\]$'
/home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
Oct  9 05:38:10.363: Unexpected error:
    <*errors.errorString | 0xc003c0aca0>: {
        s: "expected pod \"pod-subpath-test-secret-4jlw\" success: Gave up after waiting 5m0s for pod \"pod-subpath-test-secret-4jlw\" to be \"Succeeded or Failed\"",
    }
    expected pod "pod-subpath-test-secret-4jlw" success: Gave up after waiting 5m0s for pod "pod-subpath-test-secret-4jlw" to be "Succeeded or Failed"
occurred
/home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/util.go:743
				
				Click to see stdout/stderrfrom junit_03.xml

Find pod-subpath-test-secret-4jlw mentions in log files | View test history on testgrid


kubetest Test 35m41s

error during ./hack/ginkgo-e2e.sh --node-os-distro=windows --docker-config-file=/etc/docker-cred/config.json --ginkgo.focus=\[Conformance\]|\[NodeConformance\]|\[sig-windows\]|\[sig-apps\].CronJob|\[sig-api-machinery\].ResourceQuota|\[sig-network\].EndpointSlice --ginkgo.skip=\[LinuxOnly\]|\[Serial\]|\[Slow\]|\[alpha\]|GMSA|Guestbook.application.should.create.and.stop.a.working.application|device.plugin.for.Windows --report-dir=/logs/artifacts --disable-log-dump=true: exit status 1
				from junit_runner.xml

Filter through log files | View test history on testgrid


Show 307 Passed Tests

Show 6551 Skipped Tests