f61c50baa4
The last assertion in the test is very sensitive to changes. The constant has already been increased from 0 to 1 due to flakiness. The old comment explains it. In the following patch, we change the CDC generation publisher so that it clears the obsolete CDC generations earlier. This change would make this assertion flaky again. After restarting the servers, the new topology coordinator could remove the first generation if it became obsolete. This operation appends a new entry to the log. If it happened after triggering snapshot, the assertion could fail with `2 <= 1`. We could increase the constant again to unflake the test, but we better improve it once and for all. We change the assertion so that it's not sensitive to changes in the code based on Raft. The explanation is in the new comment.
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.