This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 7 failed / 323 succeeded
Started2023-01-29 17:07
Elapsed1h2m
Revisionmaster
control_plane_node_os_imagecos-85-13310-1308-1
job-versionv1.24.11-rc.0.6+7c685ed7305e76
kubetest-versionv20230127-9396ca613c
revisionv1.24.11-rc.0.6+7c685ed7305e76
worker_node_os_imagecos-85-13310-1308-1

Test Failures


Kubernetes e2e suite [sig-network] Services should serve multiport endpoints from pods [Conformance] 5m3s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-network\]\sServices\sshould\sserve\smultiport\sendpoints\sfrom\spods\s\s\[Conformance\]$'
test/e2e/framework/framework.go:652
Jan 29 17:39:02.025: Unexpected error:
    <*errors.errorString | 0xc0001f81b0>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred
test/e2e/framework/pods.go:107
				
				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 as non-root user and at a non-default path [NodeConformance] [Conformance] 7m44s

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\sas\snon\-root\suser\sand\sat\sa\snon\-default\spath\s\[NodeConformance\]\s\[Conformance\]$'
test/e2e/framework/framework.go:652
Jan 29 17:48:42.085: Timed out after 300.000s.
Expected
    <v1.PodPhase>: Failed
to equal
    <v1.PodPhase>: Succeeded
test/e2e/common/node/runtime.go:156
				
				Click to see stdout/stderrfrom junit_03.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-node] Variable Expansion should allow substituting values in a container's args [NodeConformance] [Conformance] 5m41s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-node\]\sVariable\sExpansion\sshould\sallow\ssubstituting\svalues\sin\sa\scontainer\'s\sargs\s\[NodeConformance\]\s\[Conformance\]$'
test/e2e/framework/framework.go:652
Jan 29 17:39:58.197: Unexpected error:
    <*errors.errorString | 0xc001514f30>: {
        s: "expected pod \"var-expansion-7348be4a-0545-4671-a0f2-33bf82ad1392\" success: Gave up after waiting 5m0s for pod \"var-expansion-7348be4a-0545-4671-a0f2-33bf82ad1392\" to be \"Succeeded or Failed\"",
    }
    expected pod "var-expansion-7348be4a-0545-4671-a0f2-33bf82ad1392" success: Gave up after waiting 5m0s for pod "var-expansion-7348be4a-0545-4671-a0f2-33bf82ad1392" to be "Succeeded or Failed"
occurred
test/e2e/framework/util.go:770
				
				Click to see stdout/stderrfrom junit_03.xml

Find var-expansion-7348be4a-0545-4671-a0f2-33bf82ad1392 mentions in log files | View test history on testgrid


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

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\[Conformance\]$'
test/e2e/framework/framework.go:652
Jan 29 17:40:12.013: Unexpected error:
    <*errors.errorString | 0xc003df3d80>: {
        s: "expected pod \"pod-subpath-test-configmap-8vtw\" success: Gave up after waiting 5m0s for pod \"pod-subpath-test-configmap-8vtw\" to be \"Succeeded or Failed\"",
    }
    expected pod "pod-subpath-test-configmap-8vtw" success: Gave up after waiting 5m0s for pod "pod-subpath-test-configmap-8vtw" to be "Succeeded or Failed"
occurred
test/e2e/framework/util.go:770
				
				Click to see stdout/stderrfrom junit_02.xml

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


Kubernetes e2e suite [sig-windows] [Feature:WindowsHostProcessContainers] [MinimumKubeletVersion:1.22] HostProcess containers should run as a process on the host/node 11s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-windows\]\s\[Feature\:WindowsHostProcessContainers\]\s\[MinimumKubeletVersion\:1\.22\]\sHostProcess\scontainers\sshould\srun\sas\sa\sprocess\son\sthe\shost\/node$'
test/e2e/windows/host_process.go:88
Jan 29 17:30:10.958: Expected
    <v1.PodPhase>: Failed
to equal
    <v1.PodPhase>: Succeeded
test/e2e/windows/host_process.go:134
				
				Click to see stdout/stderrfrom junit_02.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-windows] [Feature:WindowsHostProcessContainers] [MinimumKubeletVersion:1.22] HostProcess containers should support various volume mount types 3m27s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-windows\]\s\[Feature\:WindowsHostProcessContainers\]\s\[MinimumKubeletVersion\:1\.22\]\sHostProcess\scontainers\sshould\ssupport\svarious\svolume\smount\stypes$'
test/e2e/windows/host_process.go:422
Jan 29 17:37:31.610: wait for pod "host-process-volume-mounts" to finish running
Expected success, but got an error:
    <*errors.errorString | 0xc001868180>: {
        s: "Gave up after waiting 3m0s for pod \"host-process-volume-mounts\" to be \"Succeeded or Failed\"",
    }
    Gave up after waiting 3m0s for pod "host-process-volume-mounts" to be "Succeeded or Failed"
test/e2e/framework/pods.go:257
				
				Click to see stdout/stderrfrom junit_04.xml

Find host-process-volume-mounts mentions in log files | View test history on testgrid


kubetest 38m3s

error during /home/prow/go/src/sigs.k8s.io/windows-testing/gce/run-e2e.sh --node-os-distro=windows -prepull-images=true --ginkgo.focus=\[Conformance\]|\[NodeConformance\]|\[sig-windows\]|\[Feature:Windows\] --ginkgo.skip=\[LinuxOnly\]|\[Serial\]|\[alpha\]|\[Slow\]|\[GMSA\]|Guestbook.application.should.create.and.stop.a.working.application|device.plugin.for.Windows|\[sig-api-machinery\].Aggregator|\[Driver:.windows-gcepd\]: exit status 1
				from junit_runner.xml

Filter through log files | View test history on testgrid


Show 323 Passed Tests

Show 6661 Skipped Tests