Roy Dahan

@yarongilor please make sure you fully test it and add the links to Argus here.

> Fixed and tested in: When you're claiming as tested but referring to FAILED un-investigated tests, with nothing in their "Discussion" tab, what do you expect us to do?

@aleksbykov , @temichus if we need to test this variation of configuration for long term, then this configuration should be part of plans and tests of future releases.

I saw the same issue (I think) here: https://argus.scylladb.com/test/8764d79e-d785-4b99-9c70-99e2f24d0a18/runs?additionalRuns[]=b3091312-ac66-4ca5-86ff-35e1fa8c8dec @fruch who should own this?

> > what branch should Jenkins job target > > is running asymmetric-cluster test the right choice or should we choose different one? > > > > @roydahan @fruch could...

Tested the new job for CI with various nemesis_seeds (in order to fix it with a specific one later): https://argus.scylladb.com/tests/scylla-cluster-tests/1adffeeb-28ac-432c-a6f8-8477b70fa557 For now it seems like the CI job is very...

I was working to add more partitions to the test so the workload will be more balanced across the shards, but now I need to stablize it a bit since...

Yes, this is the new job: https://jenkins.scylladb.com/view/scylla-drivers/job/scylla-drivers/job/gocql/job/extended-ci/job/longevity-large-partitions-with-network-nemesis-1h-test/

It's probably a transient issue with spot availability. IIRC, we should have an automatic fallback in this case, I can check that. Another option is to trigger it for now...

Sent https://github.com/scylladb/scylla-cluster-tests/pull/9180 to add the fallback by default.