[
https://issues.apache.org/jira/browse/CASSANDRA-17349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17517518#comment-17517518
]
Brandon Williams commented on CASSANDRA-17349:
----------------------------------------------
Looks like this fell off butler, but we know from CASSANDRA-17140 that this is
caused by the USE statement, so I removed it
[here|https://github.com/driftx/cassandra-dtest/tree/CASSANDRA-17349], and
[here's a repeated
run|https://app.circleci.com/pipelines/github/driftx/cassandra/428/workflows/e0369658-6263-4321-ba8b-bc432c5b9460/jobs/5009].
> Fix flaky test -
> dtest-novnode.repair_tests.repair_test.TestRepair.test_simple_sequential_repair
> ------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-17349
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17349
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Repair
> Reporter: Brandon Williams
> Assignee: Brandon Williams
> Priority: Normal
> Fix For: 3.0.x
>
>
> Failed 2 times in the last 9 runs. Flakiness: 37%, Stability: 77%
> Error Message
> cassandra.DriverException: ID mismatch while trying to reprepare (expected
> b'ba2c66a4f13080265ea718e037637d4a', got
> b'52faf62235132756a26828817a81168d'). This prepared statement won't work
> anymore. This usually happens when you run a 'USE...' query after the
> statement was prepared.
> Stacktrace
> self = <repair_tests.repair_test.TestRepair object at 0x7ff6850f5a60>
> def test_simple_sequential_repair(self):
> """
> Calls simple repair test with a sequential repair
> """
> > self._simple_repair(sequential=True)
> repair_tests/repair_test.py:363:
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
