Cezar Moise

~~https://github.com/scylladb/scylla-cluster-tests/commit/734bfb4cf03f78bee3953d3ae55b90d4bf9d3d41 update workload on grow larger test case to be the same as grow smaller, since they use the same instance types~~ Undid changes, it's too much for a 'i4i.large'...

Ci is failing due to https://github.com/scylladb/scylla-cluster-tests/issues/10450

Changes: - https://github.com/scylladb/scylla-cluster-tests/pull/9305/commits/cf3c25725d7ed467c9e8ca0c5911d6c5b2632efd: uses only existing nemesis and parameters for tests - https://github.com/scylladb/scylla-cluster-tests/pull/9305/commits/79e27826691139145e3dd1e475897e68e5b97340: updated commit message - https://github.com/scylladb/scylla-cluster-tests/pull/9305/commits/d9f61e10b4846c8ddea0770a570e9d84d2d3c6ed: add parameter to allow longevity test to grow with a different cluster...

@scylladb/qa-maintainers please review

closed if favor of https://github.com/scylladb/scylla-cluster-tests/pull/10999, https://github.com/scylladb/scylla-cluster-tests/pull/11000 and https://github.com/scylladb/scylla-cluster-tests/pull/11001

So the test should fail on that assert, instead of continuing?

> Why is it needed? By continuing, it leads to issues with other nemesis that affect topology, like GrowShrinkCluster.

I will do a jenkins run to check for issues

> I would recommend add some linter that can identify those, and configure it specific to check those files in CI. > > I think ruff might be use to...

> I will do a jenkins run to check for issues https://jenkins.scylladb.com/view/master/job/scylla-master/job/byo/job/dtest-byo/564/ Ran without issues