# HG changeset patch
# User FUJIWARA Katsunori <foozy@lares.dti.ne.jp>
# Date 1539328028 -32400
# Node ID b7ba1cfba1741d3f3930bf7f7228e708b67fb6ac
# Parent  f9e3044d16d02a009ef22f3491d2e27c49938fc0
tests: configure fsmonitor.mode=paranoid always if fsmonitor is used

This forces fsmonitor extension execute "paranoid" code path.

Strict speaking, we should make fsmonitor-run-tests.py accept own
specific options, but there is no code path, which is disabled in
"paranoid" mode, at least now. Therefore, this solution seems
reasonable enough.

diff -r f9e3044d16d0 -r b7ba1cfba174 tests/fsmonitor-run-tests.py
--- a/tests/fsmonitor-run-tests.py	Mon Oct 08 13:12:06 2018 +0900
+++ b/tests/fsmonitor-run-tests.py	Fri Oct 12 16:07:08 2018 +0900
@@ -123,6 +123,12 @@
         runtestsargv.extend([
             '--extra-config',
             'extensions.fsmonitor=',
+            # specify fsmonitor.mode=paranoid always in order to force
+            # fsmonitor extension execute "paranoid" code path
+            #
+            # TODO: make fsmonitor-run-tests.py accept specific options
+            '--extra-config',
+            'fsmonitor.mode=paranoid',
             '--blacklist',
             blacklist,
         ])