Rohan K

``` === RUN TestDaemonPodSuite/TestMarkDaemonedPodSucceeded Submitting workflow daemoned-pod-completed- Waiting 1m0s for workflow metadata.name=daemoned-pod-completed-x6jsz ? daemoned-pod-completed-x6jsz Workflow 0s ● daemoned-pod-completed-x6jsz Workflow 0s └ ● daemoned-pod-completed-x6jsz DAG 0s └ ◷ daemoned Pod 0s...

@juliev0 actually I did a rebase and force push which re-triggered the tests, the same tests are failing again. I think the reason behind this is that in some tests...

@juliev0 the error is not because of the rebase, ig it is because of some bug in pod deletion logic

@juliev0 @sarabala1979 the issue occurs when running multiple tests, some pods are being terminated without being labelled as completed from the previous test, preventing the next test from being run....

This bug was caused after the commit https://github.com/go-git/go-git/commit/320db9af8ba8b0046e833013504eb07c61a3573c on the [go-git](https://github.com/go-git/go-git) upstream. This commit was supposed to allow us to fetch a new depth on a shallow clone (more details...

I believe the failing tests are flaky, they are not related to my change and are working on my local environment

Hey @irevoire, I've added the following panels for request rate by status code and error rate by status code in the grafana dashboard.

Hey @reddymh, sure you can raise a PR

They also sent this mail to everyone

@tpaschalis I was looking for an option to configure a single endpoint for serving multiple integrations, just like in [fluent bit](https://docs.fluentbit.io/manual/pipeline/outputs/prometheus-exporter) where you can configure what needs to be exposed....