You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Curiously, if I run just tests individually, they do not panic:
ok github.com/GoogleContainerTools/skaffold/pkg/skaffold/build/cluster (cached)
ok github.com/GoogleContainerTools/skaffold/pkg/skaffold/build/local 0.288s
ok github.com/GoogleContainerTools/skaffold/pkg/skaffold/debug 0.364s
ok github.com/GoogleContainerTools/skaffold/pkg/skaffold/deploy 0.496s
ok github.com/GoogleContainerTools/skaffold/pkg/skaffold/kubernetes 0.336s
ok github.com/GoogleContainerTools/skaffold/pkg/skaffold/kubernetes/portforward 1.207s
ok github.com/GoogleContainerTools/skaffold/pkg/skaffold/trigger 0.215s
This reeks of global state and abstraction leakage. My instinct says that there are two bugs: one within CheckDeepEqual / go-cmp, and one in a specific test being executed that poisons the other tests.
make test
on my machine has several tests that fail with the same panic message, all from uses of go-cmp.For example:
This is on macOS 10.14.6, go 1.14rc1, and Docker is not installed.
The text was updated successfully, but these errors were encountered: