8bd92d4dd0
The PR fixes a test flakiness issue in test_mv_backlog related to reading metrics. The first commit fixes a more general issue in the ScyllaMetrics helper class where it doesn't return the value of all matching lines when a specific shard is requested, but it breaks after the first match. The second commit fixes a test issue where it expects exactly one write to be throttled, not taking into account other internal writes that may be executed during this time. Fixes https://github.com/scylladb/scylladb/issues/23139 backport to improve CI stability - test only change - (cherry picked from commit5c28cffdb4) - (cherry picked from commit276a09ac6e) Parent PR: #25279 Closes scylladb/scylladb#25475 * github.com:scylladb/scylladb: test: test_mv_backlog: fix to consider internal writes test/pylib/rest_client: fix ScyllaMetrics filtering
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.