* The new abort command explicitly represents the abortion flow in mutation streaming, clearly identifying operations that are intentionally aborted. This reduces ambiguity around failures in streaming operations. * In the error-handling section, aborted operations are now explicitly marked as the cause of the streaming failure. This allows us to differentiate them from genuine errors and appropriately adjust log severity to reduce unnecessary alarm caused by aborted streaming failures. * To avoid alarming users with excessive error logs, log severity for streaming failures caused by aborted operations has been downgraded. This helps keep logs cleaner and prevents unnecessary concerns. * A new feature has been added to ensure mixed clusters during updates do not receive unsupported RPC messages, improving compatibility and stability. fixes: https://github.com/scylladb/scylladb/issues/23076 Closes scylladb/scylladb#23214
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.