Artsiom Mishuta

@Deexie could you please add Argus link?

https://argus.scylladb.com/tests/scylla-cluster-tests/90f6e442-1eca-4efc-afbe-9d2012f3e963

@elcallio, @kostja, looks like after https://github.com/scylladb/scylladb/issues/17069 and https://github.com/scylladb/scylla-cluster-tests/pull/7176. "commit log directory exceed the limit" again. could you please take a look at the failure? Should I just increase "time gate"...

> [@aleksbykov](https://github.com/aleksbykov) , could you please confirm if we really need to restart the node during changing twcs settings? @raphaelsc, could you please provide your opinion regarding this?

@timtimb0t , what is the status of this PR? Can we fix this issue before the next Weekly run?

> @timtimb0t , what is the status of this PR? Can we fix this issue before the next Weekly run? Please provide some test run.

issue fixed in https://github.com/scylladb/scylladb/pull/22069

@yaronkaikov Could you please clarify @xtrey questions What I see.. in https://jenkins.scylladb.com/job/scylla-master/job/scylla-ci/14552 is ``` [coredumps_jenkins-scylla-master-scylla-ci-14552.tar.zst](https://jenkins.scylladb.com/job/scylla-master/job/scylla-ci/14552/artifact/coredumps_jenkins-scylla-master-scylla-ci-14552.tar.zst) 18 Jan 2025, 20:46:14 3.82 GiB ``` and test.py logs (x86_64) is about 80MB so...

2 minutes? i see 1st result report ``` t:2024-06-29 03:22:52,894 f:operations_thread.py l:156 c:ScanOperationThread p:DEBUG > +------------------------+--------------------+------------+------------------+----------------+---------+---------------------------------------------------------------------------+ < t:2024-06-29 03:22:52,894 f:operations_thread.py l:156 c:ScanOperationThread p:DEBUG > | op_type | duration | exceptions...

> > > probably failed for the same root cause of #8292 > > > > > > @yarongilor #8292 is now closed, that meaning this can be closed ?...