As mentioned, this is approach 1 at fixing #132. See also approach 2 at #134.
It works, but it makes the test to take longer (as they were taking before I added this bug) and is somehow flaky, since it is obliged to measure time, and time can skew based on CI load.
Best reviewed commit-per-commit, since commit 1 adds the repro and commit 2 adds the fix.
As mentioned, this is approach 1 at fixing #132. See also approach 2 at #134.
It works, but it makes the test to take longer (as they were taking before I added this bug) and is somehow flaky, since it is obliged to measure time, and time can skew based on CI load.
Best reviewed commit-per-commit, since commit 1 adds the repro and commit 2 adds the fix.
Fixes #132.