Israel Fruchter

@Annamikhlin 1) did you downgrade the java version ? 2) did you find references of those logs in jenkins master, so we can cross check if it's still happening ?

give it a go with job known to reproduce it: - [ ] :clock1: https://jenkins.scylladb.com/job/scylla-staging/job/fruch/job/artifacts-ami-test/26/

> > [@Annamikhlin](https://github.com/Annamikhlin) > > > > 1. did you downgrade the java version ? > > 2. did you find references of those logs in jenkins master, so we...

started the process of updating the SCT builders in: https://github.com/scylladb/scylla-cluster-tests/pull/9586

@Annamikhlin I've run into it again: https://jenkins.scylladb.com/job/scylla-enterprise/job/perf-regression/job/scylla-enterprise-perf-regression-latency-650gb-elasticity/25/pipeline-console/?selected-node=19 so we might be barking the wrong tree, i.e. it's not the java version, but something else...

@Annamikhlin I'll move forward with upgrade of the jvm on the builder side and if that won't help I'll limit SCT builder to 1 executer, for the time being.

happened again in: https://jenkins.scylladb.com/job/scylla-master/job/perf-regression/job/scylla-master-perf-regression-latency-650gb-with-nemesis/39/

limiting the executors to 1, didn't helped, issue still happening across the board

@Annamikhlin I've updated the SCT builder with newer java version 2 days ago can you check in logs if this issue happened since ?

If you want to run the exact same command ? round_robin=False should do the trick Otherwise you need to run the 4 different command with round_robin=True, and wait/verify results only...