eb241a7048
The test used a real-time sleep to move the queued permit into the preemptive-abort window. If the reactor did not get CPU for long enough, admission could run only after the permit's timeout had expired, making the expected abort path flaky. The test also exhausted memory together with count resources, so the queued permit could wait for memory. Preemptive abort is intentionally not applied to permits waiting for memory, so keep enough memory available and assert that the permit is queued only on count. Use an immediate preemptive-abort threshold and a long finite timeout to exercise admission-time abort without relying on scheduler timing. Fixes: SCYLLADB-1796 Closes scylladb/scylladb#29736
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.