Roy Dahan
Roy Dahan
Waiting for it to reproduce. @soyacz I see that it was opened for 5.0 to 2022.1.x. I don't think we backported the fix to these versions. Let's backport if we...
@soyacz is it possible that the fix you did in SCT to SIGABRT the command when it's stuck hide this issue? I know that it should produce a coredump, but...
ok. in that case, we can close the issue and reopen if it appears again.
Please add another criteria that tools are added to test suites like dtest and SCT.
Removing the high label, since all runs after this fail (at least 10) on master passed without any issue.
The runs of 5.1 and 2022.2 also pass now, so @syuu1228 I don't mind to close this issue.
According to @rayakurl (please add the details) this is still failing in 5.1.rc3. Adding back to 5.1 and putting the high lable.
There is a PR waiting for backport - https://github.com/scylladb/scylladb/issues/11359
Yes On Wed, Oct 19, 2022 at 1:10 PM Raya Kurlyand ***@***.***> wrote: > @roydahan - do you still need the details? > > — > Reply to this email...
If nothing was fixed, I don't see a reason why wouldn't it reproduce. Whoever want to reproduce, need to run the same longevity with the same sequence of nemesis.