diff options
| author | Nikolaus Rath <Nikolaus@rath.org> | 2016-02-23 15:44:51 -0800 |
|---|---|---|
| committer | Nikolaus Rath <Nikolaus@rath.org> | 2016-10-28 14:07:23 -0700 |
| commit | 31bf6ca63ccb06e264475729e3642d3d8c30cea7 (patch) | |
| tree | bbaa9fd00046cfae4102bbc63879e9cad0a7911b | |
| parent | e7541d5f28330b0c85dc082d818a0f741f5279cb (diff) | |
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
| -rw-r--r-- | tests/common.py | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tests/common.py b/tests/common.py index 9373654..af5ed3c 100644 --- a/tests/common.py +++ b/tests/common.py @@ -31,7 +31,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 |