e11450ccca
The test is currently flaky. With `remove_dead_nodes_with == "remove"`, it sends several ALTER KEYSPACE requests. The request performed just after adding 3 new nodes can unexpectedly be sent twice to two different nodes by the driver. The second receiver rejects the request through the new guardrail added in2e7ba1f8ce, and the test fails. This has been acknowledged as a bug in the Python driver. It shouldn't retry non-idempotent requests with the default retry policy. There could be one more bug in the driver, as it looks like the driver decides to resend the request after it disconnects from the first receiver. The first receiver has just bootstrapped, so the driver shouldn't disconnect. We deflake the test by reconnecting the driver before performing the problematic ALTER KEYSPACE request. The change has been tested in byo, as the failure reproduces only in CI. Without the change, the test fails once in ~250 runs in dev mode. With the change, more than 1000 runs passed. Fixes #27862 No backport needed as2e7ba1f8ceis only in master. Closes scylladb/scylladb#28290
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.