Petr Hála
Petr Hála
> [@pehala](https://github.com/pehala) , [@Lakshmipathi](https://github.com/Lakshmipathi) - I'll need a detailed timeline here. We wish to push it to the cloud, I'm very concerned without enough SCT coverage. @Lakshmipathi verified with manual...
@aleksbykov Is https://github.com/scylladb/scylla-cluster-tests/pull/10636 addressing this exact issue?
Could we expedite this PR? it is failing on every run for our daily SCT runs
@yarongilor Please share more details about what was happening at the cluster at that time. If you feel like there was nothing important please state what you checked as well
Lets test that PR with the new version (there is PR open for that in SCT) and ignore this issue unless it comes up in the new version
> looks like longevity added some mechanism to inspect tombstones, and it's causing the problem when parsing large files. > > [@pehala](https://github.com/pehala) please take it from here. @yarongilor do we...
> yes, there's `run_tombstone_gc_verification` SCT parameter that runs `self.run_tombstone_gc_verification_thread(**tombstone_gc_verification_params)`. It verifies no unexpected post-repair sstable tombstone exist. So we can think of several alternatives like: try overcome the cache issue...
> I think we should backport the rule, and apply on branches as well similar to what we did for `ruff format` > > otherwise it would be painful to...
> I think doing each at a time would make sense, not all rules just moves things around, and not all of them are autofix > and not all of...
My proposed order of action here is to merge this PR and I will manually fix the backports once they are created. There shouldnt be a delay of more than...