This job view page is being replaced by Spyglass soon. Check out the new job view.
PRomertuc: Fix failing `test/e2e/storage/csi_mock_volume.go` test
ResultABORTED
Tests 8 failed / 11 succeeded
Started2022-08-16 17:18
Elapsed16m44s
Revision345f516644ee79b3f29bc281981d9d395d08f9a3
Refs 111859

Test Failures


verify conformance-yaml 2m48s

make verify WHAT=conformance-yaml
# k8s.io/kubernetes/test/e2e/storage
test/e2e/storage/csi_mock_volume.go:1743:30: undefined: test
!!! [0816 17:27:16] Call tree:
!!! [0816 17:27:16]  1: /home/prow/go/src/k8s.io/kubernetes/hack/lib/golang.sh:921 kube::golang::build_binaries_for_platform(...)
!!! [0816 17:27:16]  2: hack/make-rules/build.sh:27 kube::golang::build_binaries(...)
!!! [0816 17:27:17] Call tree:
!!! [0816 17:27:17]  1: hack/make-rules/build.sh:27 kube::golang::build_binaries(...)
!!! [0816 17:27:17] Call tree:
!!! [0816 17:27:17]  1: hack/make-rules/build.sh:27 kube::golang::build_binaries(...)
				
				Click to see stdout/stderrfrom junit_verify.xml

Filter through log files | View test history on testgrid


verify e2e-test-ownership 3.66s

make verify WHAT=e2e-test-ownership
# k8s.io/kubernetes/test/e2e/storage
test/e2e/storage/csi_mock_volume.go:1743:30: undefined: test
!!! [0816 17:28:35] Call tree:
!!! [0816 17:28:35]  1: /home/prow/go/src/k8s.io/kubernetes/hack/lib/golang.sh:921 kube::golang::build_binaries_for_platform(...)
!!! [0816 17:28:35]  2: hack/make-rules/build.sh:27 kube::golang::build_binaries(...)
!!! [0816 17:28:35] Call tree:
!!! [0816 17:28:35]  1: hack/make-rules/build.sh:27 kube::golang::build_binaries(...)
!!! [0816 17:28:35] Call tree:
!!! [0816 17:28:35]  1: hack/make-rules/build.sh:27 kube::golang::build_binaries(...)
!!! [0816 17:28:35] Call tree:
!!! [0816 17:28:35]  1: hack/make-rules/../../hack/verify-e2e-test-ownership.sh:206 ensure_dependencies(...)
				
				Click to see stdout/stderrfrom junit_verify.xml

Filter through log files | View test history on testgrid


verify generated-device-plugin 0.23s

make verify WHAT=generated-device-plugin
Can't connect to 'docker' daemon.  please fix and retry.

Possible causes:
  - Docker Daemon not started
    - Linux: confirm via your init system
    - macOS w/ Docker for Mac: Check the menu bar and start the Docker application
  - DOCKER_HOST hasn't been set or is set incorrectly
    - Linux: domain socket is used, DOCKER_* should be unset. In Bash run `unset ${!DOCKER_*}`
    - macOS w/ Docker for Mac: domain socket is used, DOCKER_* should be unset. In Bash run `unset ${!DOCKER_*}`
  - Other things to check:
    - Linux: User isn't in 'docker' group.  Add and relogin.
      - Something like 'sudo usermod -a -G docker ${USER}'
      - RHEL7 bug and workaround: https://bugzilla.redhat.com/show_bug.cgi?id=1119282#c8
				
				Click to see stdout/stderrfrom junit_verify.xml

Filter through log files | View test history on testgrid


verify generated-kms 0.23s

make verify WHAT=generated-kms
Can't connect to 'docker' daemon.  please fix and retry.

Possible causes:
  - Docker Daemon not started
    - Linux: confirm via your init system
    - macOS w/ Docker for Mac: Check the menu bar and start the Docker application
  - DOCKER_HOST hasn't been set or is set incorrectly
    - Linux: domain socket is used, DOCKER_* should be unset. In Bash run `unset ${!DOCKER_*}`
    - macOS w/ Docker for Mac: domain socket is used, DOCKER_* should be unset. In Bash run `unset ${!DOCKER_*}`
  - Other things to check:
    - Linux: User isn't in 'docker' group.  Add and relogin.
      - Something like 'sudo usermod -a -G docker ${USER}'
      - RHEL7 bug and workaround: https://bugzilla.redhat.com/show_bug.cgi?id=1119282#c8
				
				Click to see stdout/stderrfrom junit_verify.xml

Filter through log files | View test history on testgrid


verify generated-kubelet-plugin-registration 0.22s

make verify WHAT=generated-kubelet-plugin-registration
Can't connect to 'docker' daemon.  please fix and retry.

Possible causes:
  - Docker Daemon not started
    - Linux: confirm via your init system
    - macOS w/ Docker for Mac: Check the menu bar and start the Docker application
  - DOCKER_HOST hasn't been set or is set incorrectly
    - Linux: domain socket is used, DOCKER_* should be unset. In Bash run `unset ${!DOCKER_*}`
    - macOS w/ Docker for Mac: domain socket is used, DOCKER_* should be unset. In Bash run `unset ${!DOCKER_*}`
  - Other things to check:
    - Linux: User isn't in 'docker' group.  Add and relogin.
      - Something like 'sudo usermod -a -G docker ${USER}'
      - RHEL7 bug and workaround: https://bugzilla.redhat.com/show_bug.cgi?id=1119282#c8
				
				Click to see stdout/stderrfrom junit_verify.xml

Filter through log files | View test history on testgrid


verify generated-pod-resources 0.21s

make verify WHAT=generated-pod-resources
Can't connect to 'docker' daemon.  please fix and retry.

Possible causes:
  - Docker Daemon not started
    - Linux: confirm via your init system
    - macOS w/ Docker for Mac: Check the menu bar and start the Docker application
  - DOCKER_HOST hasn't been set or is set incorrectly
    - Linux: domain socket is used, DOCKER_* should be unset. In Bash run `unset ${!DOCKER_*}`
    - macOS w/ Docker for Mac: domain socket is used, DOCKER_* should be unset. In Bash run `unset ${!DOCKER_*}`
  - Other things to check:
    - Linux: User isn't in 'docker' group.  Add and relogin.
      - Something like 'sudo usermod -a -G docker ${USER}'
      - RHEL7 bug and workaround: https://bugzilla.redhat.com/show_bug.cgi?id=1119282#c8
				
				Click to see stdout/stderrfrom junit_verify.xml

Filter through log files | View test history on testgrid


verify generated-protobuf 0.91s

make verify WHAT=generated-protobuf
Can't connect to 'docker' daemon.  please fix and retry.

Possible causes:
  - Docker Daemon not started
    - Linux: confirm via your init system
    - macOS w/ Docker for Mac: Check the menu bar and start the Docker application
  - DOCKER_HOST hasn't been set or is set incorrectly
    - Linux: domain socket is used, DOCKER_* should be unset. In Bash run `unset ${!DOCKER_*}`
    - macOS w/ Docker for Mac: domain socket is used, DOCKER_* should be unset. In Bash run `unset ${!DOCKER_*}`
  - Other things to check:
    - Linux: User isn't in 'docker' group.  Add and relogin.
      - Something like 'sudo usermod -a -G docker ${USER}'
      - RHEL7 bug and workaround: https://bugzilla.redhat.com/show_bug.cgi?id=1119282#c8
				
				Click to see stdout/stderrfrom junit_verify.xml

Filter through log files | View test history on testgrid


verify generated-runtime 0.22s

make verify WHAT=generated-runtime
Can't connect to 'docker' daemon.  please fix and retry.

Possible causes:
  - Docker Daemon not started
    - Linux: confirm via your init system
    - macOS w/ Docker for Mac: Check the menu bar and start the Docker application
  - DOCKER_HOST hasn't been set or is set incorrectly
    - Linux: domain socket is used, DOCKER_* should be unset. In Bash run `unset ${!DOCKER_*}`
    - macOS w/ Docker for Mac: domain socket is used, DOCKER_* should be unset. In Bash run `unset ${!DOCKER_*}`
  - Other things to check:
    - Linux: User isn't in 'docker' group.  Add and relogin.
      - Something like 'sudo usermod -a -G docker ${USER}'
      - RHEL7 bug and workaround: https://bugzilla.redhat.com/show_bug.cgi?id=1119282#c8
!!! [0816 17:33:07] Call tree:
!!! [0816 17:33:07]  1: hack/make-rules/../../hack/verify-generated-runtime.sh:61 verify_generated_code(...)
				
				Click to see stdout/stderrfrom junit_verify.xml

Filter through log files | View test history on testgrid


Show 11 Passed Tests