Add tests/README. ctdb_test_env and, therefore, run_tests can now be
authorMartin Schwenke <martin@meltin.net>
Fri, 9 Jan 2009 06:52:38 +0000 (17:52 +1100)
committerMartin Schwenke <martin@meltin.net>
Fri, 9 Jan 2009 06:52:38 +0000 (17:52 +1100)
commit91972a6bfc18044298e77008a97ce58ecc6e6aa9
tree27896346f83de23185bba9af8a3254e523d5828b
parentfbda11b106219983145f25ef493740cacd4ea671
Add tests/README.  ctdb_test_env and, therefore, run_tests can now be
run from the tests subdirectory... and most other sensible places.
Rename $CTDB_TEST_REMOTE_SCRIPTS_DIR to $CTDB_TEST_REMOTE_DIR since it
is now intented that this directory can contain test binaries too.
daemons_start() now passes a full path to the events.d directory when
starting ctdbd.  Also fixed the path to ctdbd.  41_ctdb_ban.sh and
42_ctdb_unban.sh fail immediately if they fail to select a test node.

Signed-off-by: Martin Schwenke <martin@meltin.net>
(This used to be ctdb commit 3ecce31d3a3f72b9fa851ac99291865c119e551e)
ctdb/tests/README [new file with mode: 0644]
ctdb/tests/scripts/ctdb_test_env
ctdb/tests/scripts/ctdb_test_functions.bash
ctdb/tests/scripts/run_tests
ctdb/tests/simple/41_ctdb_ban.sh
ctdb/tests/simple/42_ctdb_unban.sh