f89235517d
The test topology_custom/test_alternator::test_localnodes_broadcast_rpc_address sets up nodes with a silly "broadcast rpc address" and checks that Alternator's "/localnodes" requests returns it correctly. The problem is that although we don't use CQL in this test, the test framework does open a CQL connection when the test starts, and closes it when it ends. It turns out that when we set a silly "broadcast RPC address", the driver tends to try to connect to it when shutting down, I'm not even sure why. But the choice of the silly address was 1.2.3.4 is unfortunate, because this IP address is actually routable - and the driver hangs until it times out (in practice, in a bit over two minutes). This trivial patch changes 1.2.3.4 to 127.0.0.0 - and equally silly address but one to which connections fail immediately. Before this patch, the test often takes more than 2 minutes to finish on my laptop, after this patch, it always finishes in 4-5 seconds. Fixes #22744 Signed-off-by: Nadav Har'El <nyh@scylladb.com> Closes scylladb/scylladb#22746
Scylla in-source tests.
For details on how to run the tests, see docs/dev/testing.md
Shared C++ utils, libraries are in lib/, for Python - pylib/
alternator - Python tests which connect to a single server and use the DynamoDB API unit, boost, raft - unit tests in C++ cqlpy - Python tests which connect to a single server and use CQL topology* - tests that set up clusters and add/remove nodes cql - approval tests that use CQL and pre-recorded output rest_api - tests for Scylla REST API Port 9000 scylla-gdb - tests for scylla-gdb.py helper script nodetool - tests for C++ implementation of nodetool
If you can use an existing folder, consider adding your test to it. New folders should be used for new large categories/subsystems, or when the test environment is significantly different from some existing suite, e.g. you plan to start scylladb with different configuration, and you intend to add many tests and would like them to reuse an existing Scylla cluster (clusters can be reused for tests within the same folder).
To add a new folder, create a new directory, and then
copy & edit its suite.ini.