503d4f014c
Currently, when a max purgeable timestamp is computed, there is no information where it comes from and how the value was obtained. Take compaction, if there are memtables or other uncompacting sstables possibly shadowing data, the timestamp is decreased to ensure a tombstone is not purged but the caller does not know what that the timestamp has its value. In this patch, we extend the return type of max_purgeable_fn to contain not only a timestamp but also an information on how it was computed. This information will be required to collect statistics on tombstone purge failures due to overlapping memtables/uncompacting sstables that come later in the series.
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.