=== RUN TestErrorSpam/setup
error_spam_test.go:81: (dbg) Run: out/minikube-windows-amd64.exe start -p nospam-117500 -n=1 --memory=3072 --wait=false --log_dir=C:\Users\jenkins.minikube6\AppData\Local\Temp\nospam-117500 --driver=docker
error_spam_test.go:81: (dbg) Done: out/minikube-windows-amd64.exe start -p nospam-117500 -n=1 --memory=3072 --wait=false --log_dir=C:\Users\jenkins.minikube6\AppData\Local\Temp\nospam-117500 --driver=docker: (1m5.7823602s)
error_spam_test.go:96: unexpected stderr: "! Failing to connect to https://registry.k8s.io/ from inside the minikube container"
error_spam_test.go:96: unexpected stderr: "* To pull new external images, you may need to configure a proxy: https://minikube.sigs.k8s.io/docs/reference/networking/proxy/"
error_spam_test.go:110: minikube stdout:
* [nospam-117500] minikube v1.36.0 on Microsoft Windows 10 Enterprise N 10.0.19045.6282 Build 19045.6282
- KUBECONFIG=C:\Users\jenkins.minikube6\minikube-integration\kubeconfig
- MINIKUBE_FORCE_SYSTEMD=
- MINIKUBE_HOME=C:\Users\jenkins.minikube6\minikube-integration\.minikube
- MINIKUBE_LOCATION=21409
- MINIKUBE_SUPPRESS_DOCKER_PERFORMANCE=true
* Using the docker driver based on user configuration
* Using Docker Desktop driver with root privileges
* Starting "nospam-117500" primary control-plane node in "nospam-117500" cluster
* Pulling base image v0.0.47-1756936034-21409 ...
* Configuring bridge CNI (Container Networking Interface) ...
* Verifying Kubernetes components...
- Using image gcr.io/k8s-minikube/storage-provisioner:v5
* Enabled addons: storage-provisioner, default-storageclass
* Done! kubectl is now configured to use "nospam-117500" cluster and "default" namespace by default
error_spam_test.go:111: minikube stderr:
! Failing to connect to https://registry.k8s.io/ from inside the minikube container
* To pull new external images, you may need to configure a proxy: https://minikube.sigs.k8s.io/docs/reference/networking/proxy/
--- FAIL: TestErrorSpam/setup (65.79s)