dc89e2ea37
test_alternator_proxy_protocol starts a node and connects via the alternator ports. Starting a node, by default, waits until the CQL ports are up. This does not guarantee that the alternator ports are up (they will be up very soon after this), so there is a short window where a connection to the alternator ports will fail. Fix by adding a ServerUpState=SERVING mode, which waits for the node to report to its supervisor (systemd, which we are pretending to be) that its ports are open. The test is then adjusted to request this new ServerUpState. Fixes #28210 Fixes #28211 Flaky tests are only in master and branch-2026.1, so backporting there. - (cherry picked from commitebac810c4e) - (cherry picked from commit59f2a3ce72) Parent PR: #28291 Closes scylladb/scylladb#28443 * github.com:scylladb/scylladb: test: test_alternator_proxy_protocol: wait for the node to report itself as serving test: cluster_manager: add ability to wait for supervisor STATUS=serving
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.