[
https://issues.apache.org/jira/browse/CASSANDRA-18635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17817318#comment-17817318
]
Berenguer Blasi commented on CASSANDRA-18635:
---------------------------------------------
I have mixed feelings here. I 'solved' the present failure in a way everything
makes sense to me. But this new failure makes me wonder if there is sthg
fundamentally wrong in CASSANDRA-17851 or if it's just another case of unlucky
async races.
I _do_ understand this ticket's failure, or so I think, but not the one you
bring. They might end up being the same thing or not. I vote to get this into
review to get an extra pair of eyes but I would be inclined to open a new
ticket. Reasoning being that this failure is on a race on tooling, whereas the
new one is on not interrupting compactions while upgrading, which seems like a
fundamental behavioral problem.
> Test failure: org.apache.cassandra.distributed.test.UpgradeSSTablesTest
> -----------------------------------------------------------------------
>
> Key: CASSANDRA-18635
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18635
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
> Reporter: Brandon Williams
> Assignee: Berenguer Blasi
> Priority: Normal
> Fix For: 5.0-rc, 5.x
>
>
> Seen here:
> https://app.circleci.com/pipelines/github/driftx/cassandra/1095/workflows/6114e2e3-8dcc-4bb0-b664-ae7d82c3349f/jobs/33405/tests
> {noformat}
> junit.framework.AssertionFailedError: expected:<0> but was:<2>
> at
> org.apache.cassandra.distributed.test.UpgradeSSTablesTest.upgradeSSTablesInterruptsOngoingCompaction(UpgradeSSTablesTest.java:86)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
