Be more lenient in timings test

Timing tests are by nature flaky, especially in CI, see python-trio/trio#1851 for example.
elastic · Mar 30, 2022 · 7d7f8d4 · 7d7f8d4
1 parent 2f1ee14
commit 7d7f8d4
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/tests/driver/runner_test.py b/tests/driver/runner_test.py
@@ -5795,13 +5795,13 @@ async def test_adds_request_timings(self):
         assert len(timings) == 3
 
         assert timings[0]["operation"] == "initial-call"
-        assert math.isclose(timings[0]["service_time"], 0.1, rel_tol=0.05)
+        assert timings[0]["service_time"] == pytest.approx(0.1, abs=0.1)
 
         assert timings[1]["operation"] == "stream-a"
-        assert math.isclose(timings[1]["service_time"], 0.2, rel_tol=0.05)
+        assert timings[1]["service_time"] == pytest.approx(0.2, abs=0.1)
 
         assert timings[2]["operation"] == "stream-b"
-        assert math.isclose(timings[2]["service_time"], 0.1, rel_tol=0.05)
+        assert timings[2]["service_time"] == pytest.approx(0.1, abs=0.1)
 
         # common properties
         for timing in timings: