[
https://issues.apache.org/jira/browse/CASSANDRA-18676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17744547#comment-17744547
]
Berenguer Blasi edited comment on CASSANDRA-18676 at 7/19/23 10:51 AM:
-----------------------------------------------------------------------
So it is definitely
[flaky|https://app.circleci.com/pipelines/github/bereng/cassandra/1020/workflows/5455461e-7b4b-4702-9a8c-42b034c5f979/jobs/23675/tests]
in trunk but in a different way. I haven't been able to repro the original
reported exceptions...
was (Author: bereng):
So it is definitely flaky in trunk but in a different way. I haven't been able
to repro the original reported exceptions...
> CorruptedSSTablesCompactionsTest is flaky
> -----------------------------------------
>
> Key: CASSANDRA-18676
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18676
> Project: Cassandra
> Issue Type: Bug
> Components: Local/SSTable, Test/unit
> Reporter: Branimir Lambov
> Priority: Normal
> Fix For: 5.x
>
>
> See e.g. [this
> run|https://app.circleci.com/pipelines/github/blambov/cassandra/510/workflows/fd484f76-b0f0-48c9-8672-d73bdc36b8ec/jobs/13575/tests].
> The test was looked at for CASSANDRA-15879, but it is still failing from time
> to time. One of the failures appears to be introduced by CASSANDRA-14227 and
> the others by CASSANDRA-18134. The failures are genuine problems with
> handling corruption, not just test issues.
> The {{CorruptSSTableException}} paths in {{SSTableIdentityIterator}} should
> likely also catch {{AssertionError}} and {{IllegalArgumentException}}, and
> most probably the tombstone verification should be done on the read path.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
