=== RUN TestPause/serial/Start
pause_test.go:80: (dbg) Run: out/minikube-darwin-amd64 start -p pause-20220801164333-3161 --memory=2048 --install-addons=false --wait=all --driver=hyperkit
=== CONT TestPause/serial/Start
pause_test.go:80: (dbg) Non-zero exit: out/minikube-darwin-amd64 start -p pause-20220801164333-3161 --memory=2048 --install-addons=false --wait=all --driver=hyperkit : exit status 90 (58.187219975s)
-- stdout --
* [pause-20220801164333-3161] minikube v1.26.0 on Darwin 12.5
- MINIKUBE_LOCATION=14695
- KUBECONFIG=/Users/jenkins/minikube-integration/darwin-amd64-hyperkit--14695-1971-16c8c96838ca145d17ecca8303180c41961a99dd/kubeconfig
- MINIKUBE_BIN=out/minikube-darwin-amd64
- MINIKUBE_SUPPRESS_DOCKER_PERFORMANCE=true
- MINIKUBE_HOME=/Users/jenkins/minikube-integration/darwin-amd64-hyperkit--14695-1971-16c8c96838ca145d17ecca8303180c41961a99dd/.minikube
* Using the hyperkit driver based on user configuration
* Starting control plane node pause-20220801164333-3161 in cluster pause-20220801164333-3161
* Creating hyperkit VM (CPUs=2, Memory=2048MB, Disk=20000MB) ...
-- /stdout --
** stderr **
X Exiting due to RUNTIME_ENABLE: Temporary Error: sudo crictl version: Process exited with status 1
stdout:
stderr:
time="2022-08-01T23:44:31Z" level=fatal msg="connect: connect endpoint 'unix:///var/run/cri-dockerd.sock', make sure you are running as root and the endpoint has been started: context deadline exceeded"
*
╭─────────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ * If the above advice does not help, please let us know: │
│ https://github.com/kubernetes/minikube/issues/new/choose │
│ │
│ * Please run `minikube logs --file=logs.txt` and attach logs.txt to the GitHub issue. │
│ │
╰─────────────────────────────────────────────────────────────────────────────────────────────╯
** /stderr **
pause_test.go:82: failed to start minikube with args: "out/minikube-darwin-amd64 start -p pause-20220801164333-3161 --memory=2048 --install-addons=false --wait=all --driver=hyperkit " : exit status 90
helpers_test.go:222: -----------------------post-mortem--------------------------------
helpers_test.go:239: (dbg) Run: out/minikube-darwin-amd64 status --format={{.Host}} -p pause-20220801164333-3161 -n pause-20220801164333-3161
helpers_test.go:239: (dbg) Non-zero exit: out/minikube-darwin-amd64 status --format={{.Host}} -p pause-20220801164333-3161 -n pause-20220801164333-3161: exit status 6 (139.624238ms)
-- stdout --
Running
WARNING: Your kubectl is pointing to stale minikube-vm.
To fix the kubectl context, run `minikube update-context`
-- /stdout --
** stderr **
E0801 16:44:31.591411 11857 status.go:413] kubeconfig endpoint: extract IP: "pause-20220801164333-3161" does not appear in /Users/jenkins/minikube-integration/darwin-amd64-hyperkit--14695-1971-16c8c96838ca145d17ecca8303180c41961a99dd/kubeconfig
** /stderr **
helpers_test.go:239: status error: exit status 6 (may be ok)
helpers_test.go:241: "pause-20220801164333-3161" host is not running, skipping log retrieval (state="Running\nWARNING: Your kubectl is pointing to stale minikube-vm.\nTo fix the kubectl context, run `minikube update-context`")
--- FAIL: TestPause/serial/Start (58.33s)