Israel Fruchter

@pehala are you following this one ? (seems like nix tests are not having the ccm command available, you might need to prefix it with some `nix` command...)

> @fruch @pehala I saw you in the git blame output for the test file in question - https://github.com/scylladb/scylla-cluster-tests/blame/3988be290645b072a568072ded0f09b6cddf3320/test-cases/longevity/longevity-alternator-3h.yaml#L4 > Can you help answer the above? What I think is...

> > > [@ptrsmrn](https://github.com/ptrsmrn) - what's the next step here? > > > > > > [@mykaul](https://github.com/mykaul) I asked [@nyh](https://github.com/nyh) if he can take a look as I don't think...

@pehala I think we should backport the rule, and apply on branches as well similar to what we did for `ruff format` otherwise it would be painful to backport (this...

> > I think we should backport the rule, and apply on branches as well similar to what we did for `ruff format` > > otherwise it would be painful...

I would recommend doing the manual changes separately, in its own commits. For clearly reviewing those, and for backporting so those won't be together with the automated ones, also we...

@pehala @soyacz this looks o.k., but the name change in reporting to argus is gonna be annoying when we'll want to compare to older releases results @soyacz we should plan...

> > @pehala @soyacz > > this looks o.k., but the name change in reporting to argus is gonna be annoying when we'll want to compare to older releases results...

> > > Each case is different. Here, if we want to keep the names matched, we need info how to match nemesis name with disrupt function. @fruch @roydahan if...

> I'm fine with either approach as long as we have the stats and able to compare releases after the change either way we are not removing anything from Argus...