47a66d0150
There are four stages left to handle: cleanup, cleanup_target, end_migration and revert_migration. All are handling removed nodes already, so the PR just extends the test. fixes: #16527 Closes scylladb/scylladb#17684 * github.com:scylladb/scylladb: test/tablets_migration: Test revert_migration failure handling test/tablets_migration: Test end_migration failure handling test/tablets_migration: Test cleanup_target failure handling test/tablets_migration: Test cleanup failure handling test/tablets_migration: Prepare for do_... stages test/tablets_migration: Add ability to removenode via any other node test/tablets_migration: Wrap migration stages failing code into a helper class storage_service: Add failure injection to crash cleanup_tablet
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++ cql-pytest - 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.