summaryrefslogtreecommitdiff
path: root/test/sample.conf
diff options
context:
space:
mode:
authorClay Gerrard <clay.gerrard@gmail.com>2013-07-19 01:39:42 -0700
committerClay Gerrard <clay.gerrard@gmail.com>2013-07-19 01:39:42 -0700
commit1f43ee050b94d368182d1d6e0340416ea1436e76 (patch)
tree7633b3934ef6816140411b0266b4767b8817c0c0 /test/sample.conf
parent39b48e1e9f785945e45b2b5f0f38b6763a8f1458 (diff)
downloadswift-1f43ee050b94d368182d1d6e0340416ea1436e76.tar.gz
Add option to make probetests more brittle
Currently probetests take advantage of a number of assumptions about the SUT. Unfortunately after some time with a working SAIO, configuration drift may result in a system that is no longer compatible with these assumptions. To help weary developers more quickly identify the changes they've made since they last ran probetests successfully, some handy validators have been added to test.probe.common Additionally a new option 'validate_rsync' in test.conf, when enabled, will run a series of up front validations during the setup of each probetest by inspecting the ring, the mounted devices, and the rsync exports ("modules") in order to ensure that when probetests fail the do so early and with specific complaints. To preserve existing failures, the option is disabled by default. Change-Id: I2be11c7e67ccd0bc0589c360c170049b6288c152
Diffstat (limited to 'test/sample.conf')
-rw-r--r--test/sample.conf1
1 files changed, 1 insertions, 0 deletions
diff --git a/test/sample.conf b/test/sample.conf
index 49a83f709..32d984e0d 100644
--- a/test/sample.conf
+++ b/test/sample.conf
@@ -47,3 +47,4 @@ fake_syslog = False
[probe_test]
# check_server_timeout = 30
+# validate_rsync = false