f45465b9f6
After PR https://github.com/scylladb/scylladb/pull/28396 reduced the test volumes to 20MiB to speed up test_out_of_space_prevention.py, keeping the original 0.8 critical disk utilization threshold can make the tests flaky: transient disk usage (e.g. commitlog segment churn) can push the node into ENOSPC during the run. These tests do not write much data, so reduce the critical disk utilization threshold to 0.5. With 20MiB volumes this leaves ~10MiB of headroom for temporary growth during the test. Fixes: https://github.com/scylladb/scylladb/issues/28463 Closes scylladb/scylladb#28593
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.