The test_drop_quarantined_sstables test could fail due to a race between compaction and quarantining of SSTables. If compaction selects an SSTable before it is moved to quarantine, and change_state is called during compaction, the SSTable may already be removed, resulting in a std::filesystem_error due to missing files. This patch resolves the issue by wrapping the quarantine operation inside run_with_compaction_disabled(). This ensures compaction is paused on the compaction group view while SSTables are being quarantined, preventing the race. Additionally, updates the test to quarantine up to 1/5 SSTables instead of one randomly and increases the number of sstables genereted to improve test scenario. Fixes scylladb/scylladb#25487 Closes scylladb/scylladb#25494
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.