test: fix fuzzy_test timeout in release mode

The multishard_query_test/fuzzy_test was timing out (SIGKILL after
15 minutes) in release mode CI.

In release mode the test generates up to 64 partitions with up to
1000 clustering rows and 1000 range tombstones each.  With deeply
nested randomly-generated types (e.g. frozen<map<varint,
frozen<map<frozen<tuple<...>>>>>>), this volume of data can exceed
the 15-minute CI timeout.

Reduce the release-mode clustering-row and range-tombstone
distributions from 0-1000 to 0-200.  This caps the worst case at
~12,800 rows -- still 2x the devel-mode maximum (0-100) and
sufficient to exercise multi-partition paged scanning with many
pages.

Fixes: SCYLLADB-1270
This commit is contained in:
Piotr Smaron
2026-03-31 16:47:48 +02:00
parent ab43420d30
commit df2924b2a3

View File

@@ -1160,9 +1160,15 @@ SEASTAR_THREAD_TEST_CASE(fuzzy_test) {
std::uniform_int_distribution<size_t>(0, 100), // clustering-rows
std::uniform_int_distribution<size_t>(0, 100), // range-tombstones
#else
// Keep these values moderate: with complex randomly-generated
// schemas (deeply nested frozen collections/UDTs), large row
// counts cause data generation and paged scanning to be very
// slow, leading to CI timeouts. The test's value comes from
// schema variety and paging correctness, not from sheer data
// volume.
std::uniform_int_distribution<size_t>(32, 64), // partitions
std::uniform_int_distribution<size_t>(0, 1000), // clustering-rows
std::uniform_int_distribution<size_t>(0, 1000), // range-tombstones
std::uniform_int_distribution<size_t>(0, 200), // clustering-rows
std::uniform_int_distribution<size_t>(0, 200), // range-tombstones
#endif
tests::default_timestamp_generator());