Petr Hála

> 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...

The action works almost correctly, it adds correct commit into the file, but in the commit msg it lists too many commits

Important change here is also the fact, the names of the nemesis changed to the name of the class instead of the method, which might be a breaking change

> One more thing to consider when thinking about moving logic under specific nemeses: some of them use logic/methods from another one. Need to think how to approach this -...

v2: * Rebased * Fix CategoricalMonkey * Also updated it with usage of nemesis_seed and selectors * Fix rest of the tests

v3: * Move logic out of `__init__` into `disrupt` method * Rebase on latest master * Use `NemesisFlags` for flags filtering * Simplify `NemesisRegistry` logic * Ignore AbstractClasses in Nemesis...

@fruch given that you closed github.com/scylladb/argus/issues/798 and that you were the one who requested backwards compatibility in the first, does this mean I can progress with this PR without any...

Revived this PR, it is ready for another review. I am looking for approval for the design of the solution, afterwards I will begin full on testing and finalizing. v4:...

Ready for review. I updated the cover letter with latest updates and I would like to push this forward @scylladb/qa-maintainers, let me know if something is not clear or if...

Both tests passed ok, singular nemesis run and longevity run (killed by spot termination), results are in cover letter. @scylladb/qa-maintainers Please take a look, I think it is ready for...