# Last week in scylla-cluster-tests.git master (issue #158; 2026-10-30)

**URL:** <https://forum.scylladb.com/t/last-week-in-scylla-cluster-tests-git-master-issue-158-2026-10-30/5561>\
**Category:** ScyllaDB\
**Tags:** git-testing-news\
**Created:** [October 30, 2026, 6:35pm UTC](https://forum.scylladb.com/t/last-week-in-scylla-cluster-tests-git-master-issue-158-2026-10-30/5561 "2026-10-30T18:35:06Z")\
**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:** [October 30, 2026, 6:35pm UTC](https://forum.scylladb.com/t/last-week-in-scylla-cluster-tests-git-master-issue-158-2026-10-30/5561/1 "2026-10-30T18:35:06Z")

</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 66002be6…18fa4e44 range are covered.

There were 47 non-merge commits from 10 authors in that period. Some notable commits:

SCT [moved to Python 3.15](https://github.com/scylladb/scylla-cluster-tests/commit/a7f1294a7450435249fc075475dbf231335d9894) in the hydra image and in the devcontainer. Local environments now need uv 0.13.0 or later.

The trigger-matrix CLI can now [trigger one matrix for several Scylla versions in one run](https://github.com/scylladb/scylla-cluster-tests/commit/66002be660791dee56233cd6076165bf1f6b1e59) and show the results as a [job-by-version grid](https://github.com/scylladb/scylla-cluster-tests/commit/5172c08d8d3619bfed6de10abd79a730068a528e). With `supported_versions_only` set and no version given, a matrix [runs the latest release of every supported Scylla version](https://github.com/scylladb/scylla-cluster-tests/commit/c2bd1ef6599ba8d4f32f48ad393b76022eaa03d5).

The `scylla-doctor-gating` trigger matrix [got the features of the sd-release-gating pipeline](https://github.com/scylladb/scylla-cluster-tests/commit/f8406635cf7f6d52bdb17db8d9cee48865e34d8c) and now [runs the full sd-release-gating operating system set](https://github.com/scylladb/scylla-cluster-tests/commit/63f36a03b2ae16bb31e6b35a8a1aa1de7cc73079), so it can replace that pipeline.

A [1-DB-node variant of the predefined throughput-steps perf test](https://github.com/scylladb/scylla-cluster-tests/commit/bf7710833fae3f280c93a6779755d505cd439dba) runs with RF=1 on AWS i7i and i8g instances, with one Jenkins job per instance type.

Bare-metal hosts without a free data disk can run Scylla on the root filesystem with the new [`scylla_setup_no_raid` option](https://github.com/scylladb/scylla-cluster-tests/commit/c6143ba20dd53824da42ce7506a5f72a167ef3ca). The cleanup also [restores a bare-metal host to its state before the run](https://github.com/scylladb/scylla-cluster-tests/commit/69f8a29f4a1f21e2f5109bf6d63ce696b19adc19), including its packages and services.

xcloud scaling tests now [cover scale-out and scale-up in separate pipelines](https://github.com/scylladb/scylla-cluster-tests/commit/f05e7eaa3bb0a119f9a0c1bde847e362e5eaa359). The scale-out pipeline uses a [scaling config pinned to the i8g.large instance type](https://github.com/scylladb/scylla-cluster-tests/commit/1f6be0a501caf0656863de7db81ecb14be618938), and SCT resolves the instance type names to Cloud API IDs.

As part of the Python 3.15 move, [`scylla-driver` was updated to 3.29.12](https://github.com/scylladb/scylla-cluster-tests/commit/a7f1294a7450435249fc075475dbf231335d9894), which adds Python 3.15 wheels, `TABLETS_ROUTING_V2` support and TLS session resumption. The release also drops the eventlet, gevent and Twisted event loops.

Minicloud [moved to v0.10.0](https://github.com/scylladb/scylla-cluster-tests/commit/71891b37d98a0d5f3721d0347fce14ca5409474b), which adds lightweight VM ceilings per instance type and per tag. Its DB guests also [stop Scylla reactor polling](https://github.com/scylladb/scylla-cluster-tests/commit/18fa4e4494632178e49cd60e59ba60a5e570944e), controlled by the new `minicloud_scylla_overcommitted_cpu` setting.

A new plan describes [nested sections for the SCT configuration](https://github.com/scylladb/scylla-cluster-tests/commit/2b1200ce6813fae45d5e2c6c7d7a568a0dc04bfd), with the nemesis section as the pilot. A mini-plan covers [cheaper artifact tests and a retry after a spot reclaim](https://github.com/scylladb/scylla-cluster-tests/commit/ba7cbc43b7e3cf6bb3cc3224991e79ad725df582).

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