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

**URL:** <https://forum.scylladb.com/t/last-week-in-scylla-cluster-tests-git-master-issue-137-2026-05-22/5376>\
**Category:** ScyllaDB\
**Tags:** git-testing-news\
**Created:** [May 22, 2026, 5:47pm UTC](https://forum.scylladb.com/t/last-week-in-scylla-cluster-tests-git-master-issue-137-2026-05-22/5376 "2026-05-22T17:47:26Z")\
**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 22, 2026, 5:47pm UTC](https://forum.scylladb.com/t/last-week-in-scylla-cluster-tests-git-master-issue-137-2026-05-22/5376/1 "2026-05-22T17:47:26Z")

</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 868b3ff0…b2093b44 range are covered.

There were 30 non-merge commits from 11 authors in that period. Some notable commits:

Cloud provisioning saw a wave of capacity-awareness work across backends. AWS gained [automatic AZ fallback on capacity errors in the modern provisioning path](https://github.com/scylladb/scylla-cluster-tests/commit/8b20c9b50093252e65d987a2f5998beb9c05ce45), gated by `fallback_to_next_availability_zone` , default true. GCE got the same treatment with [upfront AZ filtering and dynamic zone discovery](https://github.com/scylladb/scylla-cluster-tests/commit/5a72b47d44f71144095e1fd6b8a27b4e307817e9).

The AWS [VPC peering layer was rewritten](https://github.com/scylladb/scylla-cluster-tests/commit/d6a4539d63b2b1ce58aac9e81190968d583a562c) with VPC-ID-based lookup, proper `accept_vpc_peering_connection()` with retries on the post-creation timing window, `CreatedBy=SCT` tagging, programmatic cleanup of blackhole routes and rejected peerings, and a `dry_run` mode. Fixes the long-standing root cause of unaccepted peerings (target VPC’s `accept()` swallowing `OperationNotPermitted`).

The Migrator integration now [reports P99 write latency, throughput, dataset size, speed and duration to Argus](https://github.com/scylladb/scylla-cluster-tests/commit/f48ab3bae43089aa84d95e4b1731fc4ca62edd78). xcloud’s weekly provisioning trigger gained [VS-on-ScyllaCloud node deployment](https://github.com/scylladb/scylla-cluster-tests/commit/b3c9fd060f93dd1781fe544033026c7aea4b8022) to catch deployment regressions earlier.

The bundled latte version was bumped twice — first to [v0.47.0](https://github.com/scylladb/scylla-cluster-tests/commit/7deedb53b222a1271279e7ab889119a428812be2) bringing a rune `0.13` →`0.14` upgrade, Alternator API enhancements, a `workloads/alternator/type_validation.rn` fix and an `openssl` security update, then to [v0.47.1](https://github.com/scylladb/scylla-cluster-tests/commit/f4403f0fadf1f1e23552ac5d11df0409907d2670) which switches rune to a fork carrying a compiler-divergence fix and bumps `openssl` again.

The `cql-stress` version was [updated to v0.2.9](https://github.com/scylladb/scylla-cluster-tests/commit/4ddbf13693ce4bcbfe8f991ddf182433128c3857), focused on dependencies upgrade.

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