Roy Dahan
Roy Dahan
Sorry, but I'm still not convinced it should be a nemesis. It can be a special feature test in SCT or special longevity that do the above + revoke the...
Or a Scylla issue that claims this error is expected. And if it does, why is it an error?
The work here should not be lost, someone should change this PR from a nemesis to a feature test in SCT.
Assigning to @temichus, this should be taken to their group and decide what's the expected result and what's a reasonable timeout. Then, they can decide on solution. (Their mandate is...
> @roy have a PR that should be addressing this Do I? Maybe you mixed it with another PR I have for the 200k rows?
Fine by me.
First, I created a separate "epic" task to optimize test setup time (#7242 ). In this case, the issue is that SCT couldn't detect the provided scylla version, probably it...
This should wait for a scylla issue if we know backtraces that are still multi-line. Also, all backports cannot happen until (probably never) the change will reach the old branches.
You can send the PR to SCT to remove the mulit-line support. The only problem is that we won't be able to use newer version of SCT to test an...
Moving or not moving?