Open enekofb opened 1 year ago
happened also
panic: Log in goroutine after TestWatcher_Stop has completed: "level"=0 "msg"="faked"
goroutine 22 [running]:
testing.(*common).logDepth(0xc000140b60, {0xc0003cc798, 0x18}, 0x3)
/opt/hostedtoolcache/go/1.20.3/x64/src/testing/testing.go:1003 +0x4e7
testing.(*common).log(...)
/opt/hostedtoolcache/go/1.20.3/x64/src/testing/testing.go:985
testing.(*common).Log(0xc000140b60, {0xc00052fd18?, 0x0?, 0x0?})
/opt/hostedtoolcache/go/1.20.3/x64/src/testing/testing.go:1026 +0x4e
github.com/go-logr/logr/testr.testlogger.Info({{0x0, {0x1f3dad0, 0x0}, {0x0, 0x0, 0x0}, {0x0, 0x0}, 0x1, {0x0, ...}}, ...}, ...)
/home/runner/go/pkg/mod/github.com/go-logr/logr@v1.2.3/testr/testr.go:95 +0x18e
github.com/go-logr/logr.Logger.Info({{0x1f5d540?, 0xc0000d60a0?}, 0x570a74?}, {0x1cd44fb, 0x5}, {0x0, 0x0, 0x0})
/home/runner/go/pkg/mod/github.com/go-logr/logr@v1.2.3/logr.go:261 +0xd0
github.com/weaveworks/weave-gitops-enterprise/pkg/query/collector/kubefakes.fakeControllerManager.Start(...)
/home/runner/work/weave-gitops-enterprise/weave-gitops-enterprise/pkg/query/collector/kubefakes/manager.go:72
github.com/weaveworks/weave-gitops-enterprise/pkg/query/collector.(*DefaultWatcher).Start.func1()
/home/runner/work/weave-gitops-enterprise/weave-gitops-enterprise/pkg/query/collector/watcher.go:196 +0x44
created by github.com/weaveworks/weave-gitops-enterprise/pkg/query/collector.(*DefaultWatcher).Start
/home/runner/work/weave-gitops-enterprise/weave-gitops-enterprise/pkg/query/collector/watcher.go:195 +0x32a
FAIL github.com/weaveworks/weave-gitops-enterprise/pkg/query/collector 0.043s
? github.com/weaveworks/weave-gitops-enterprise/pkg/query/collector/reconciler/reconcilerfakes [no test files]
? github.com/weaveworks/weave-gitops-enterprise/pkg/query/configuration [no test files]
=== RUN TestNewReconciler
Validate that this has been fixed.
Did we resolve?
needs to be validated, is in teams' next column
TestWatch paniced in CI
We removed it to dont block the release but
AC
This ticket is to followup not in the test itself but to understand whether