0de3a5f3ff
In the test_mv_topology_change case, we use an injection to delay the view updates application, so that the ERMs have a chance to change in the process. This injection was also enabled on a new node in the test, which was later decommissioned. During the shutdown, writes were still being performed, causing view update generation and delays due to the injection which in turn delayed the node shutdown, causing the test to timeout. This patch removes the injection for the node being shut down. At the same time, the force_gossip_topology_changes=True option is also removed from its config, but for that option it's enough to enable on the first node in the cluster and all nodes use it. Fixes: https://github.com/scylladb/scylladb/issues/18941 Closes scylladb/scylladb#18958
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++ cql-pytest - 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.