d6346e68c1
This PR includes two changes that make gossiper much less likely to mark nodes as down in tests unexpectedly, and cause test flakiness in issues like SCYLLADB-864: - fixing false node conviction when echo succeeds, - increasing the failure_detector_timeout fixture. Fixes: SCYLLADB-864 No need for backport: related CI failures are rare, and merging #29522 made them even more unlikely (I haven't seen one since then, but it's still possible to reproduce locally on dev machines). Closes scylladb/scylladb#29755 * github.com:scylladb/scylladb: test/cluster: increase failure_detector_timeout gossiper: fix false node conviction when echo succeeds
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.