Fix flaky test TestErrorThreshold
TestErrorThreshold uses NodeManager which has a dependency on time. Once !2552 (merged) is merged, we should plug in the new router implementation that allows for running health checks in a deterministic fashion instead of relying on time.
=== RUN TestErrorThreshold
=== RUN TestErrorThreshold/read_threshold_reached
TestErrorThreshold/read_threshold_reached: server_test.go:1018:
Error Trace: server_test.go:1018
Error: Not equal:
expected: *errors.errorString(&errors.errorString{s:"primary is not healthy"})
actual : <nil>(<nil>)
Test: TestErrorThreshold/read_threshold_reached
=== RUN TestErrorThreshold/write_threshold_reached
--- FAIL: TestErrorThreshold (0.37s)
--- FAIL: TestErrorThreshold/read_threshold_reached (0.13s)
--- PASS: TestErrorThreshold/write_threshold_reached (0.23s)