unittests: reduce paxos propose interval to increase speed

The MONs are stressed more often and there is less aggregation of the
pending requests. But the unit tests are only meant to verify that a
known code path exists and performs as expected, therefore it will not
make a difference. And if it does, it is a bug that needs fixing.

Reviewed-By: Christophe Courtaut <christophe.courtaut@gmail.com>
Signed-off-by: Loic Dachary <loic@dachary.org>

diff --git a/src/test/vstart_wrapper.sh b/src/test/vstart_wrapper.sh
index 42458564c78e42a36d027b48fd1b1e0a20a0fd02..9f0a35527cddbf05bbed11bd988e399f1103b0a5 100755 (executable)
--- a/src/test/vstart_wrapper.sh
+++ b/src/test/vstart_wrapper.sh
@@ -25,7 +25,9 @@ function vstart_setup()
     mkdir -p dev
     trap "vstart_teardown ; rm -f $TMPFILE" EXIT
     export LC_ALL=C # some tests are vulnerable to i18n
-    MON=1 OSD=3 ./vstart.sh -n -X -l mon osd || return 1
+    MON=1 OSD=3 ./vstart.sh \
+        -o 'paxos propose interval = 0.01' \
+        -n -X -l mon osd || return 1
     export PATH=.:$PATH
     export CEPH_CONF=ceph.conf