gansheer opened a new issue, #4754: URL: https://github.com/apache/camel-k/issues/4754
### What happened? While looking at some github action tests logs I noticed a few golang stacktrace that do not impact the completion/result of the tests but produce a lot of noise in the logs. One of the only relevant reference I could find was this issue: https://github.com/solo-io/gloo/issues/8548. It could be a result of [zap upgrade](https://github.com/apache/camel-k/pull/4748). ### Steps to reproduce Look into an github action raw logs ([common](https://github.com/apache/camel-k/actions/workflows/common.yml?query=branch%3Amain)) -- preferably on passing tests. ### Relevant log output ```shell The trace is: 2023-09-15T13:52:02.6249978Z [controller-runtime] log.SetLogger(...) was never called, logs will not be displayed: 2023-09-15T13:52:02.6250380Z goroutine 42 [running]: 2023-09-15T13:52:02.6250665Z runtime/debug.Stack() 2023-09-15T13:52:02.6251487Z /opt/hostedtoolcache/go/1.20.8/x64/src/runtime/debug/stack.go:24 +0x65 2023-09-15T13:52:02.6252078Z sigs.k8s.io/controller-runtime/pkg/log.eventuallyFulfillRoot() 2023-09-15T13:52:02.6252726Z /home/runner/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/log/log.go:59 +0xbd ``` ``` ### Camel K version main branch -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
