36870feb29
This change was created in the same spirit off8221b960f. The S3ProxyServer (introduced in8919e0abab) currently prints its status directly to stdout, which can be distracting when reviewing test results. For example: ```console $ ./test.py --mode release object_store/test_backup::test_simple_backup_and_restore Found 1 tests. Setting minio proxy random seed to 1731924995 Starting S3 proxy server on ('127.193.179.2', 9002) ================================================================================ [N/TOTAL] SUITE MODE RESULT TEST ------------------------------------------------------------------------------ [1/1] object_store release [ PASS ] object_store.test_backup.1 Stopping S3 proxy server ------------------------------------------------------------------------------ CPU utilization: 3.1% ``` Move these messages to use proper logging to give developers more control over their visibility: - Make logger parameter mandatory in S3ProxyServer constructor - Route "Stopping S3 proxy" message through the provided logger - Add --log-level option to the standalone proxy server launcher The message is now hidden: ```console $ ./test.py --mode release object_store/test_backup::test_simple_backup_and_restore Found 1 tests. ================================================================================ [N/TOTAL] SUITE MODE RESULT TEST ------------------------------------------------------------------------------ [1/1] object_store release [ PASS ] object_store.test_backup.1 ------------------------------------------------------------------------------ CPU utilization: 4.1% ``` --- this change improves the developer experience, hence no need to backport. Closes scylladb/scylladb#21610 * github.com:scylladb/scylladb: test: route S3 Proxy server messages through logger test: s3_proxy: remove unused method
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.