=== RUN TestNoKubernetes/serial/Stop
no_kubernetes_test.go:158: (dbg) Run: out/minikube-linux-amd64 stop -p NoKubernetes-109956
no_kubernetes_test.go:158: (dbg) Non-zero exit: out/minikube-linux-amd64 stop -p NoKubernetes-109956: signal: killed (253.069526ms)
-- stdout --
* Stopping node "NoKubernetes-109956" ...
-- /stdout --
no_kubernetes_test.go:160: Failed to stop minikube "out/minikube-linux-amd64 stop -p NoKubernetes-109956" : signal: killed
helpers_test.go:222: -----------------------post-mortem--------------------------------
helpers_test.go:239: (dbg) Run: out/minikube-linux-amd64 status --format={{.Host}} -p NoKubernetes-109956 -n NoKubernetes-109956
helpers_test.go:239: (dbg) Non-zero exit: out/minikube-linux-amd64 status --format={{.Host}} -p NoKubernetes-109956 -n NoKubernetes-109956: exit status 6 (234.265755ms)
-- stdout --
Running
WARNING: Your kubectl is pointing to stale minikube-vm.
To fix the kubectl context, run `minikube update-context`
-- /stdout --
** stderr **
E0924 19:25:35.786632 47472 status.go:451] kubeconfig endpoint: get endpoint: "NoKubernetes-109956" does not appear in /home/jenkins/minikube-integration/19700-3763/kubeconfig
** /stderr **
helpers_test.go:239: status error: exit status 6 (may be ok)
helpers_test.go:241: "NoKubernetes-109956" 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: TestNoKubernetes/serial/Stop (0.49s)