752e6561fb
When destroying a test cluster, ScyllaCluster.stop() calls ScyllaServer.stop() for each running server. Previously, non-zero exit status codes from scylla servers were silently ignored during test teardown. This change modifies the logging behavior to print the exit status code when a scylla server exits with a non-zero status. This helps developers quickly identify potential issues or unexpected terminations during test runs. Differences in handling: - Before: Non-zero exit codes were not logged - After: Non-zero exit codes are printed, providing visibility into server termination errors This improvement aids in diagnosing intermittent test failures or unexpected server shutdowns during test execution. Refs #21742 Signed-off-by: Kefu Chai <kefu.chai@scylladb.com> Closes scylladb/scylladb#21934
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.