# Last week in scylla-cluster-tests.git master (issue #146; 2026-07-24)

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

</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 d119adfb…d5314a5e range are covered.

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

The KeyStore now uses [AWS Secrets Manager backend](https://github.com/scylladb/scylla-cluster-tests/commit/8239266be6900d32ba21e302fbdec2053afaec65) selectable via `SCT_KEYSTORE_BACKEND` (S3 still as default).

We can run [Gemini tests on the OCI backend](https://github.com/scylladb/scylla-cluster-tests/commit/a3d4ce59482e58ee7fce8463935a25a9504554b1) (lower costs).

The trigger-matrix picked up the ability to [auto-detect AMI architecture and filter jobs accordingly](https://github.com/scylladb/scylla-cluster-tests/commit/d11d7eb91fcfcc05d97290665167337545bc345a), letting scylla-pkg trigger x86 and ARM builds separately without duplicate runs.

Nemeses can now tell whether the prepare phase is still running through a [new event that signals prepare progress](https://github.com/scylladb/scylla-cluster-tests/commit/f1f045b50228c51adc5103a3c4bc9b35b2edbaa9), so disruptions like AddRemoveDCNemesis can avoid overlapping with the prepare-to-steady-state transition.

The AWS provisioner now [reports config-init failures to Argus](https://github.com/scylladb/scylla-cluster-tests/commit/1ad02ba411589a6ad2f980df724eeac6c1d35602) instead of leaving runs in an unknown state when, for example, a package URL 404s.

A new [test-run-comparison-reports skill](https://github.com/scylladb/scylla-cluster-tests/commit/f0f81ba06fa7fcc46c5e987c1dbdf3215e8f30f8) generates Confluence-compatible HTML comparison pages across multiple SCT runs, pulling metadata from the Argus API and latency results from S3 logs with P99 pass/fail color coding.

The constraint-based sizing migration continued, converting the [gemini non-CDC/ICS test configs](https://github.com/scylladb/scylla-cluster-tests/commit/bd00a935e51762c6281b85b7b912bf3e16083064) as well as the [Manager](https://github.com/scylladb/scylla-cluster-tests/commit/11be96ee39458ea8b2334f6f331e52c9fc30e9dd) and [vector-search](https://github.com/scylladb/scylla-cluster-tests/commit/fba9cb62af1be71eb5925e4ffe3b72ff32b71714) test cases from literal instance types to `sizing_*` constraints.

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