This repository was archived by the owner on Apr 17, 2025. It is now read-only.
generated from kubernetes/kubernetes-template-project
-
Notifications
You must be signed in to change notification settings - Fork 113
Unit tests could not run #252
Labels
kind/bug
Categorizes issue or PR as related to a bug.
Comments
/assign @mochizuki875 |
/kind bug |
adrianludwin
added a commit
to adrianludwin/hierarchical-namespaces
that referenced
this issue
Feb 15, 2023
E2Es broke a few days ago, likely when test-infra upgraded to 1.20. I also couldn't run staticcheck on my Google workstation, which has 1.20, with the same failure message. Upgrading staticcheck fixed the problem; I also took the opportunity to match the test-infra krte image as well as the Golang version (which caused some minor reformatting), and also made the integ tests hermetic by including the setup-envtest tool (bug kubernetes-retired#252, based on an approach suggested in kubernetes-retired#253). Tested: couldn't build on my workstation on Go 1.20 before this change; can after it. Can also run integ tests after deleting local output of setup-envtest.
adrianludwin
added a commit
to adrianludwin/hierarchical-namespaces
that referenced
this issue
Feb 15, 2023
E2Es broke a few days ago, likely when test-infra upgraded to 1.20. I also couldn't run staticcheck on my Google workstation, which has 1.20, with the same failure message. Upgrading staticcheck fixed the problem; I also took the opportunity to match the test-infra krte image as well as the Golang version (which caused some minor reformatting), and also made the integ tests hermetic by including the setup-envtest tool (bug kubernetes-retired#252, based on an approach suggested in kubernetes-retired#253). Tested: couldn't build on my workstation on Go 1.20 before this change; can after it. Can also run integ tests after deleting local output of setup-envtest.
9 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What happened?
Unit tests (
make test
as shown in Development Workflow) could not run because the controlplane could not be started using testenv.What did you expect to happen?
I expect the controlplane to start using envtest and the unit tests are able to run.
How can we reproduce it (as minimally and precisely as possible)?
Run unit tests by executing
make test
.The error will occur as below.
Kubernetes version
OS version
Install tools
The text was updated successfully, but these errors were encountered: