mirror of
https://github.com/prometheus/prometheus.git
synced 2024-11-13 09:04:06 -08:00
7b1c0d6b66
Previously `max` results stopped reading from results in tests prematurely, as it stopped when `max` number of items were received from the channel instead of `max` number of unique target groups received. This caused flaky tests where the same target group was received multiple times, as Kubernetes informers may emit the same event multiple times. Before this patch, running this test repeatedly failed eventually. After this patch I have run the test many thousand times without failure. ```bash go test -run TestEndpointsDiscoveryNamespaces -count 1000 -test.v ``` Signed-off-by: Frederic Branczyk <fbranczyk@gmail.com> |
||
---|---|---|
.. | ||
client_metrics.go | ||
endpoints.go | ||
endpoints_test.go | ||
ingress.go | ||
ingress_test.go | ||
kubernetes.go | ||
kubernetes_test.go | ||
node.go | ||
node_test.go | ||
pod.go | ||
pod_test.go | ||
service.go | ||
service_test.go |