040d6e2245
Interval's copy and move constructors are full of branches since the two payload T:s are optional and therefore have to be optionally-constructed. This can be eliminated for trivially copyable types (like dht::token) by eliminating interval's user-defined special member functions (constructors etc) in that special case. In turn, this enables optimizations in the standard library (and our own containers) that convert moves/copies of spans of such types into memcpy(). Minor optimization, not a candidate to backport. Closes scylladb/scylladb#25841 * github.com:scylladb/scylladb: test: nonwrapping_interval_test: verify an interval of tokens is trivial interval: specialize interval_data<T> for trivial types interval: split data members into new interval_data class
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.