mirror of
https://github.com/samba-team/samba.git
synced 2024-12-23 17:34:34 +03:00
085e179dcb
Direct leak of 256 byte(s) in 8 object(s) allocated from: #0 0x7f11b90d9c08 in __interceptor_malloc (/lib64/libasan.so.5+0xefc08) #1 0x7f11b8f395df in tdb_alloc_read ../../../lib/tdb/common/io.c:696 #2 0x7f11b8f290ee in _tdb_fetch ../../../lib/tdb/common/tdb.c:274 #3 0x7f11b8f29379 in tdb_fetch ../../../lib/tdb/common/tdb.c:283 #4 0x473ecc in ltdb_fetch ../../tests/src/fake_ctdbd.c:904 #5 0x478b40 in ltdb_transaction_update ../../tests/src/fake_ctdbd.c:993 #6 0x41fef2 in ctdb_rec_buffer_traverse ../../protocol/protocol_types.c:1656 #7 0x48108b in ltdb_transaction ../../tests/src/fake_ctdbd.c:1026 #8 0x48108b in control_trans3_commit ../../tests/src/fake_ctdbd.c:2878 #9 0x48108b in client_process_control ../../tests/src/fake_ctdbd.c:4147 #10 0x48108b in client_process_packet ../../tests/src/fake_ctdbd.c:3839 #11 0x4847f5 in client_read_handler ../../tests/src/fake_ctdbd.c:3806 #12 0x44f620 in comm_read_done ../../common/comm.c:208 #13 0x7f11b8f94fe8 in _tevent_req_notify_callback ../../../lib/tevent/tevent_req.c:141 #14 0x7f11b8f951fd in tevent_req_finish ../../../lib/tevent/tevent_req.c:193 #15 0x7f11b8f95265 in _tevent_req_done ../../../lib/tevent/tevent_req.c:199 #16 0x44e876 in pkt_read_handler ../../common/pkt_read.c:133 #17 0x44f315 in comm_fd_handler ../../common/comm.c:412 #18 0x7f11b8f92896 in tevent_common_invoke_fd_handler ../../../lib/tevent/tevent_fd.c:138 #19 0x7f11b8fa6937 in epoll_event_loop ../../../lib/tevent/tevent_epoll.c:736 #20 0x7f11b8fa6937 in epoll_event_loop_once ../../../lib/tevent/tevent_epoll.c:937 #21 0x7f11b8f9f53e in std_event_loop_once ../../../lib/tevent/tevent_standard.c:110 #22 0x7f11b8f90f34 in _tevent_loop_once ../../../lib/tevent/tevent.c:772 #23 0x7f11b8f955f1 in tevent_req_poll ../../../lib/tevent/tevent_req.c:300 #24 0x485a04 in start_server ../../tests/src/fake_ctdbd.c:4450 #25 0x485a04 in main ../../tests/src/fake_ctdbd.c:4544 #26 0x7f11b8c60412 in __libc_start_main (/lib64/libc.so.6+0x24412) Signed-off-by: Swen Schillig <swen@linux.ibm.com> Reviewed-by: Volker Lendecke <vl@samba.org> Reviewed-by: Martin Schwenke <martin@meltin.net> Autobuild-User(master): Martin Schwenke <martins@samba.org> Autobuild-Date(master): Mon Aug 26 10:19:30 UTC 2019 on sn-devel-184 |
||
---|---|---|
.. | ||
complex | ||
cunit | ||
etc-ctdb/events/legacy | ||
eventd | ||
eventscripts | ||
onnode | ||
scripts | ||
shellcheck | ||
simple | ||
src | ||
takeover | ||
takeover_helper | ||
tool | ||
local_daemons.sh | ||
README | ||
run_cluster_tests.sh | ||
run_tests.sh | ||
test_check_tcp_ports.sh | ||
TODO |
Introduction ------------ For a developer, the simplest way of running most tests on a local machine from within the git repository is: make test This runs all unit tests (onnode, takeover, tool, eventscripts) and the tests against local daemons (simple) using the script tests/run_tests.sh. When running tests against a real or virtual cluster the script tests/run_cluster_tests.sh can be used. This runs all integration tests (simple, complex). Both of these scripts can also take a list of tests to run. You can also pass options, which are then passed to run_tests. However, if you just try to pass options to run_tests then you lose the default list of tests that are run. You can't have everything... tests/run_tests.sh ------------------ This script can be used to manually run all or selected unit tests and simple integration tests against local daemons. Test selection is done by specifying optional call parameters. If no parameter is given, all unit tests and simple integration tests are run. This runs all unit tests of the "tool" category: ./tests/run_tests.sh tool In order to run a single test, one simply specifies the path of the test script to run as the last parameter, e.g.: ./tests/run_tests.sh ./tests/eventscripts/00.ctdb.monitor.001 ./tests/run_tests.sh ./tests/simple/76_ctdb_pdb_recovery.sh One can also specify multiple test suites and tests: ./tests/run_tests.sh eventscripts tool ./tests/onnode/0001.sh The script also has number of command-line switches. Some of the more useful options include: -s Print a summary of tests results after running all tests -l Use local daemons for integration tests This allows the tests in "simple" to be run against local daemons. All integration tests communicate with cluster nodes using onnode or the ctdb tool, which both have some test hooks to support local daemons. By default 3 daemons are used. If you want to use a different number of daemons then do not use this option but set TEST_LOCAL_DAEMONS to the desired number of daemons instead. The -l option just sets TEST_LOCAL_DAEMONS to 3... :-) -e Exit on the first test failure -C Clean up - kill daemons and remove $TEST_VAR_DIR when done Tests uses a temporary/var directory for test state. By default, this directory is not removed when tests are complete, so you can do forensics or, for integration tests, re-run tests that have failed against the same directory (with the same local daemons setup). So this option cleans things up. Also kills local daemons associated with directory. -V Use <dir> as $TEST_VAR_DIR Use the specified temporary temporary/var directory. -H No headers - for running single test with other wrapper This allows tests to be embedded in some other test framework and executed one-by-one with all the required environment/infrastructure. This replaces the old ctdb_test_env script. How do the tests find remote test programs? ------------------------------------------- If the all of the cluster nodes have the CTDB git tree in the same location as on the test client then no special action is necessary. The simplest way of doing this is to share the tree to cluster nodes and test clients via NFS. If cluster nodes do not have the CTDB git tree then CTDB_TEST_REMOTE_DIR can be set to a directory that, on each cluster node, contains the contents of tests/scripts/ and tests/bin/. In the future this will hopefully (also) be supported via a ctdb-test package. Running the ctdb tool under valgrind ------------------------------------ The easiest way of doing this is something like: VALGRIND="valgrind -q" scripts/run_tests ... This can be used to cause all invocations of the ctdb client (and, with local daemons, the ctdbd daemons themselves) to occur under valgrind. NOTE: Some libc calls seem to do weird things and perhaps cause spurious output from ctdbd at start time. Please read valgrind output carefully before reporting bugs. :-) How is the ctdb tool invoked? ----------------------------- $CTDB determines how to invoke the ctdb client. If not already set and if $VALGRIND is set, this is set to "$VALGRIND ctdb". If this is not already set but $VALGRIND is not set, this is simply set to "ctdb" Test and debugging variable options ----------------------------------- CTDB_TEST_MODE Set this environment variable to enable test mode. This enables daemons and tools to locate their socket and PID file relative to CTDB_BASE. When testing with multiple local daemons on a single machine this does 3 extra things: * Disables checks related to public IP addresses * Speeds up the initial recovery during startup at the expense of some consistency checking * Disables real-time scheduling CTDB_DEBUG_HUNG_SCRIPT_LOGFILE=FILENAME FILENAME specifies where log messages should go when debugging hung eventscripts. This is a testing option. See also CTDB_DEBUG_HUNG_SCRIPT. No default. Messages go to stdout/stderr and are logged to the same place as other CTDB log messages. CTDB_SYS_ETCDIR=DIRECTORY DIRECTORY containing system configuration files. This is used to provide alternate configuration when testing and should not need to be changed from the default. Default is /etc. CTDB_RUN_TIMEOUT_MONITOR=yes|no Whether CTDB should simulate timing out monitor events in local daemon tests. Default is no. CTDB_TEST_SAMBA_VERSION=VERSION VERSION is a 32-bit number containg the Samba major version in the most significant 16 bits and the minor version in the least significant 16 bits. This can be used to test CTDB's checking of incompatible versions without installing an incompatible version. This is probably best set like this: export CTDB_TEST_SAMBA_VERSION=$(( (4 << 16) | 12 )) CTDB_VARDIR=DIRECTORY DIRECTORY containing CTDB files that are modified at runtime. Defaults to /usr/local/var/lib/ctdb.