Multiple tests are currently flaky due to graceful shutdown timing out when flushing tables takes more than a minute. We still don't understand why flushing is sometimes so slow, but we suspect it is an issue with new machines spider9 and spider11 that CI runs on. All observed failures happened on these machines, and most of them on spider9. In this commit, we increase the timeout of graceful shutdown as a temporary workaround to improve CI stability. When we get to the bottom of the issue and fix it, we will revert this change. Ref #12028 It's a temporary workaround to improve CI stability, we don't have to backport it. Closes scylladb/scylladb#24802
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.