tdb2: suppress failtest more than once on mmap.

Now we test failing mmap, ccanlint -v time has increased from 200 to
330 seconds.  Worse, tests no time out on my laptop.

Fix this, by preventing us from going down that particular rabbit hole.
ccanlint -v now takes 201 seconds again.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
(Imported from CCAN commit fbae37ba91ec230e34be564084099726cc3a9d47)

diff --git a/lib/tdb2/test/failtest_helper.c b/lib/tdb2/test/failtest_helper.c
index f094a5974ea26c34a54474875d7c5c04b557ebeb..3172e3ad6e150478812c6b9e33434929ee147167 100644 (file)
--- a/lib/tdb2/test/failtest_helper.c
+++ b/lib/tdb2/test/failtest_helper.c
@@ -83,6 +83,11 @@ block_repeat_failures(struct tlist_calls *history)
                return FAIL_PROBE;
        }
 
+       /* We handle mmap failing, by falling back to read/write, so
+        * don't try all possible paths. */
+       if (last->type == FAILTEST_MMAP)
+               return FAIL_PROBE;
+
        /* Unlock or non-blocking lock is fail-once. */
        if (is_unlock(last) || is_nonblocking_lock(last))
                return FAIL_PROBE;