The test process like that: - run long dns refresh process - request for the resolve hostname with short abort_source timer - result should be empty list, because of aborted request The test sometimes finishes long dns refresh before abort_source fired and the result list is not empty. There are two issues. First, as.reset() changes the abort_source timeout. The patch adds a get() method to the abort_source_timeout class, so there is no change in the abort_source timeout. Second, a sleep could be not reliable. The patch changes the long sleep inside a dns refresh lambda into condition_variable handling, to properly signal the end of the dns refresh process. Fixes: #26561 Fixes: VECTOR-268 It needs to be backported to 2025.4 Closes scylladb/scylladb#26566
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.