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
It was reported in a Debian bug that TestRegisteringHookMultipleTimesShouldBeSafe fails when the tests are run on a system with only one or two CPUs, or alternatively on non-amd64 architectures with slower CPUs. The test failure output is at the end of this issue.
The cause appears to be that the metrics server started as a goroutine in httpServePrometheusMetrics() isn't fully ready to serve requests by the time the test code attempts to make a request. As a work around for the time being, I've introduced a quarter second sleep before returning from httpServePrometheusMetrics() (which is probably overkill) that fixes this test failure.
It was reported in a Debian bug that
TestRegisteringHookMultipleTimesShouldBeSafe
fails when the tests are run on a system with only one or two CPUs, or alternatively on non-amd64 architectures with slower CPUs. The test failure output is at the end of this issue.The cause appears to be that the metrics server started as a goroutine in
httpServePrometheusMetrics()
isn't fully ready to serve requests by the time the test code attempts to make a request. As a work around for the time being, I've introduced a quarter second sleep before returning fromhttpServePrometheusMetrics()
(which is probably overkill) that fixes this test failure.The text was updated successfully, but these errors were encountered: