# Last week in scylla-cluster-tests.git master (issue #138; 2026-05-29)

**URL:** https://forum.scylladb.com/t/last-week-in-scylla-cluster-tests-git-master-issue-138-2026-05-29/5387
**Category:** ScyllaDB
**Tags:** git-testing-news
**Created:** [May 29, 2026, 4:42pm UTC](https://forum.scylladb.com/t/last-week-in-scylla-cluster-tests-git-master-issue-138-2026-05-29/5387 "2026-05-29T16:42:53Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![soyacz](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.scylladb.com/soyacz/32/557_2.png) [@soyacz](https://forum.scylladb.com/u/soyacz)
#### Post date: [May 29, 2026, 4:42pm UTC](https://forum.scylladb.com/t/last-week-in-scylla-cluster-tests-git-master-issue-138-2026-05-29/5387/1 "2026-05-29T16:42:53Z")

</div>

This short report brings to light some interesting commits to [scylla-cluster-tests.git master](https://github.com/scylladb/scylla-cluster-tests) from the last week. Commits in the 30e454f6…b1554414 range are covered.

There were 68 non-merge commits from 15 authors in that period. Some notable commits:

Tablet split/merge gained end-to-end coverage. SCT learned to [emit dedicated Tablet/Split and Tablet/Merge events](https://github.com/scylladb/scylla-cluster-tests/commit/c048269bbd09597140223a5138130c55f8975507) from `Detected tablet split/merge for table` log lines, a [new nemesis alters every user table](https://github.com/scylladb/scylla-cluster-tests/commit/251552eabc9bee2533a4fead516311bdeedc07fd) — including MV and `scylla_cdc_log` — with per-table `tablets = {"min_tablet_count": x}` to force split/merge, and a [combined LWT/MV/CDC longevity test with tablet split/merge](https://github.com/scylladb/scylla-cluster-tests/commit/38a2356650b91f1a6d0111b3cf8e3cc1c65920a4) ties it together via new Jenkins jobs.

Manager backup testing saw both new capability and a large cleanup. The sctool backup CLI was [extended with `--retention-lock-mode` and `--retention-days` for WORM backups](https://github.com/scylladb/scylla-cluster-tests/commit/24530c836e306dc21de512cbc864e84de6a5feef), exercised by a [new GCE WORM backup test](https://github.com/scylladb/scylla-cluster-tests/commit/ab9bdac3034535fcda812999fa4c8ee05f896fed) in unlocked retention mode and `test_backup_and_restore` now [exercises a full drop → restore schema → restore data flow](https://github.com/scylladb/scylla-cluster-tests/commit/647d9a5194d473e5fd9e2d8b1a78a7a6bec40d57).

Audit testing now [supports rule-based configuration](https://github.com/scylladb/scylla-cluster-tests/commit/e6aa40121235c3a5aa900bbb67ee1160b43700de), declaring an `audit_rules` field on the `ScyllaYaml` model and writing dynamically supplied rules.

Adaptive timeouts gained [per-operation multipliers](https://github.com/scylladb/scylla-cluster-tests/commit/b15544145b8d7f72244b54f2b0bae634e6608057) via a new `adaptive_timeout_multipliers` config (e.g. `decommission: 4` , `new_node: 2`) allowing adjustments when tested features affect performance of some operations.

The TWCS 48h longevity test was [retuned to ~50-70% disk utilization with ZSTD dictionary compression](https://github.com/scylladb/scylla-cluster-tests/commit/ccdfa89a0cb9a76d2f0daf1193be6e6a642de689) (partition-count 4k→20k, max-rate 30k→100k).

The bundled latte was [bumped to v0.48.0](https://github.com/scylladb/scylla-cluster-tests/commit/ec754d3b2548b00f708d5f2ef170ff0afbfe0472), upgrading rune to 0.14.2, adding projection and condition-expression support to the Alternator API, and pulling in an `astral-tokio-tar` security fix.

[CodeRabbit was configured](https://github.com/scylladb/scylla-cluster-tests/commit/d41d16296aefe84d91589da7392e40cc9f9fef14) with Jira integration and path-based instructions aligned with AGENTS.md. Evaulating it.

See you in the next issue of last week in scylla-cluster-tests.git master!