[
https://issues.apache.org/jira/browse/CASSANDRA-17070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17437409#comment-17437409
]
Andres de la Peña commented on CASSANDRA-17070:
-----------------------------------------------
I don't think we should put the duplicated cleanup logic back, in principle not
reusing MV names should be enough.
I mentioned the query timeout to indicate that the failure is not related to
what we are addressing here, so I think the run can be considered successful.
By the way,
[here|https://app.circleci.com/pipelines/github/adelapena/cassandra/1101/workflows/63014008-3d52-4d07-a5aa-748fad389ec7]
is the repeated run for j11, all green. I think we are ready to merge.
> ViewComplexTest hardening
> -------------------------
>
> Key: CASSANDRA-17070
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17070
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
> Reporter: Berenguer Blasi
> Assignee: Berenguer Blasi
> Priority: Normal
> Fix For: 4.0.x, 4.x
>
>
> I have seen a number of times already the {{ViewComplexTest}} family timeout
> on test method teardown. This leaves a dirty env behind triggering the
> following test methods to fail on it. This ticket aims at hardening them.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
