=== RUN TestMinikubeProfile
minikube_profile_test.go:44: (dbg) Run: out/minikube-darwin-amd64 start -p first-054000 --driver=hyperkit
minikube_profile_test.go:44: (dbg) Non-zero exit: out/minikube-darwin-amd64 start -p first-054000 --driver=hyperkit : exit status 90 (15.875764386s)
-- stdout --
* [first-054000] minikube v1.30.1 on Darwin 13.4.1
- MINIKUBE_LOCATION=15868
- KUBECONFIG=/Users/jenkins/minikube-integration/15868-56270/kubeconfig
- MINIKUBE_BIN=out/minikube-darwin-amd64
- MINIKUBE_SUPPRESS_DOCKER_PERFORMANCE=true
- MINIKUBE_HOME=/Users/jenkins/minikube-integration/15868-56270/.minikube
- MINIKUBE_FORCE_SYSTEMD=
* Using the hyperkit driver based on user configuration
* Starting control plane node first-054000 in cluster first-054000
* Creating hyperkit VM (CPUs=2, Memory=6000MB, Disk=20000MB) ...
-- /stdout --
** stderr **
X Exiting due to RUNTIME_ENABLE: Failed to enable container runtime: sudo systemctl restart cri-docker.socket: Process exited with status 1
stdout:
stderr:
Job failed. See "journalctl -xe" for details.
*
╭─────────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ * 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 **
minikube_profile_test.go:46: test pre-condition failed. args "out/minikube-darwin-amd64 start -p first-054000 --driver=hyperkit ": exit status 90
panic.go:522: *** TestMinikubeProfile FAILED at 2023-07-13 15:30:37.991196 -0700 PDT m=+862.527675189
helpers_test.go:222: -----------------------post-mortem--------------------------------
helpers_test.go:239: (dbg) Run: out/minikube-darwin-amd64 status --format={{.Host}} -p second-056000 -n second-056000
helpers_test.go:239: (dbg) Non-zero exit: out/minikube-darwin-amd64 status --format={{.Host}} -p second-056000 -n second-056000: exit status 85 (110.430305ms)
-- stdout --
* Profile "second-056000" not found. Run "minikube profile list" to view all profiles.
To start a cluster, run: "minikube start -p second-056000"
-- /stdout --
helpers_test.go:239: status error: exit status 85 (may be ok)
helpers_test.go:241: "second-056000" host is not running, skipping log retrieval (state="* Profile \"second-056000\" not found. Run \"minikube profile list\" to view all profiles.\n To start a cluster, run: \"minikube start -p second-056000\"")
helpers_test.go:175: Cleaning up "second-056000" profile ...
helpers_test.go:178: (dbg) Run: out/minikube-darwin-amd64 delete -p second-056000
panic.go:522: *** TestMinikubeProfile FAILED at 2023-07-13 15:30:38.465549 -0700 PDT m=+863.002028231
helpers_test.go:222: -----------------------post-mortem--------------------------------
helpers_test.go:239: (dbg) Run: out/minikube-darwin-amd64 status --format={{.Host}} -p first-054000 -n first-054000
helpers_test.go:239: (dbg) Non-zero exit: out/minikube-darwin-amd64 status --format={{.Host}} -p first-054000 -n first-054000: exit status 6 (121.546936ms)
-- stdout --
Running
WARNING: Your kubectl is pointing to stale minikube-vm.
To fix the kubectl context, run `minikube update-context`
-- /stdout --
** stderr **
E0713 15:30:38.577662 58913 status.go:415] kubeconfig endpoint: extract IP: "first-054000" does not appear in /Users/jenkins/minikube-integration/15868-56270/kubeconfig
** /stderr **
helpers_test.go:239: status error: exit status 6 (may be ok)
helpers_test.go:241: "first-054000" 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`")
helpers_test.go:175: Cleaning up "first-054000" profile ...
helpers_test.go:178: (dbg) Run: out/minikube-darwin-amd64 delete -p first-054000
helpers_test.go:178: (dbg) Done: out/minikube-darwin-amd64 delete -p first-054000: (5.272399995s)
--- FAIL: TestMinikubeProfile (21.74s)