Martin Schwenke e9df17b500 ctdb-tests: Separate custom cluster startup from test initialisation ... Separate cluster startup from test initialisation for tests that start the cluster with customised configuration. In these cases the result of the cluster startup is actually the point of the test. Additionally, pubips.013.failover_noop.sh claims to have completed test initialisation twice, which just seems wrong. The result is: * ctdb_test_init() takes one option (-n) to indicate when it should not configure/start the cluster * New function ctdb_nodes_start_custom() accepts options for special cluster configuration, only operates on local daemons and triggers a test failure rather than a test error on failure. Signed-off-by: Martin Schwenke <martin@meltin.net>		2020-07-22 02:42:38 +00:00
..
cluster.bash	ctdb-tests: Add cluster.bash include file	2019-10-04 09:41:28 +00:00
common.sh	ctdb-tests: Add function ctdb_test_check_supported_OS	2020-03-10 07:37:34 +00:00
integration_local_daemons.bash	ctdb-tests: Dump logs on shutdown failure	2020-02-18 02:56:38 +00:00
integration_real_cluster.bash	ctdb-tests: Rationalise node stop/start/restart	2020-02-18 02:56:38 +00:00
integration.bash	ctdb-tests: Separate custom cluster startup from test initialisation	2020-07-22 02:42:38 +00:00
script_install_paths.sh	ctdb-tests: Use $PWD/bin/ if it exists when running in-tree	2020-02-10 04:07:39 +00:00
test_wrap	ctdb-tests: Use "#!/usr/bin/env bash" for improved portability	2020-07-22 02:42:37 +00:00
unit.sh	ctdb-tests: Make unit.sh pass shellcheck	2020-07-22 02:42:37 +00:00