From afcadf08c20284ed324375162080d33f45621ae1 Mon Sep 17 00:00:00 2001 From: Nikolaus Rath Date: Tue, 23 Feb 2016 15:44:51 -0800 Subject: Estimate system clock granularity more conservatively Origin: debian Forwarded: no Patch-Name: clock-granularity.diff Some unit tests check that file access time stamps are updated correctly. For such a test to succeed, it's necessarily that the time between two subsequent test-accesses can actually be resolved. The heuristic to determine this granularity doesn't seem to work well on e.g. the i386 buildd, so we make it much more conservative. This means the test suite runs longer, but otherwise has no ill effects. Gbp-Pq: Name clock-granularity.diff --- tests/common.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tests/common.py b/tests/common.py index 8c3be59..bea2e5c 100644 --- a/tests/common.py +++ b/tests/common.py @@ -27,7 +27,7 @@ def get_clock_granularity(): stamp2 = time.time() resolution = min(resolution, stamp2 - stamp1) time.sleep(0.01) - return resolution + return max(1, 10 * resolution) CLOCK_GRANULARITY = get_clock_granularity() # When testing, we want to make sure that we don't sleep for too short a time -- cgit v1.2.3