panic:
Your test failed.
Ginkgo panics to prevent subsequent assertions from running.
Normally Ginkgo rescues this panic so you shouldn't see it.
But, if you make an assertion in a goroutine, Ginkgo can't capture the panic.
To circumvent this, you should call
defer GinkgoRecover()
at the top of the goroutine that caused this panic.
goroutine 1 [running]:
kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo.Fail(0xc0005a8000, 0x2d1, 0xc0001b2430, 0x1, 0x1)
/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/ginkgo_dsl.go:262 +0xc8
kubevirt.io/kubevirt/vendor/github.com/onsi/gomega/internal/assertion.(*Assertion).match(0xc0003d3080, 0x1c36c20, 0x2c29040, 0x0, 0x0, 0x0, 0x0, 0x2c29040)
/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/gomega/internal/assertion/assertion.go:75 +0x1f1
kubevirt.io/kubevirt/vendor/github.com/onsi/gomega/internal/assertion.(*Assertion).ToNot(0xc0003d3080, 0x1c36c20, 0x2c29040, 0x0, 0x0, 0x0, 0x0)
/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/gomega/internal/assertion/assertion.go:43 +0xc7
kubevirt.io/kubevirt/tests.GetHighestCPUNumberAmongNodes(0x1c9ee40, 0xc00036b960, 0xc0001b9dc0)
/go/src/kubevirt.io/kubevirt/tests/utils.go:2879 +0x1b8
kubevirt.io/kubevirt/tests_test.glob..func27.3.1()
/go/src/kubevirt.io/kubevirt/tests/vmi_configuration_test.go:142 +0x4a
...
Remediation by soft-linking the internal configuration location against the valid configuration (see #199) makes the tests work again.