[
https://issues.apache.org/jira/browse/CASSANDRA-16963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17416260#comment-17416260
]
Caleb Rackliffe commented on CASSANDRA-16963:
---------------------------------------------
Made one comment in the PR and ran the tests locally. Seeing
{{test_simple_sequential_repair}}, {{test_simple_parallel_repair}}, and a few
others fail with an error that looks something like this:
{noformat}
test_simple_sequential_repair failed and was not selected for rerun.
<class 'KeyError'>
'fully_qualified_cf'
[<TracebackEntry
/Users/maedhroz/Projects/Apache/cassandra-dtest/repair_tests/repair_test.py:363>,
<TracebackEntry
/Users/maedhroz/Projects/Apache/cassandra-dtest/repair_tests/repair_test.py:453>,
<TracebackEntry
/Users/maedhroz/Projects/Apache/cassandra-dtest/repair_tests/repair_test.py:112>,
<TracebackEntry
/Users/maedhroz/Projects/Apache/cassandra-dtest/tools/data.py:30>]
{noformat}
> Flaky test: repair_tests/repair_test.py::TestRepair::test_local_dc_repair
> -------------------------------------------------------------------------
>
> Key: CASSANDRA-16963
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16963
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
> Reporter: Alex Petrov
> Assignee: Alex Petrov
> Priority: Normal
>
> Sometimes we get “ID mismatch while trying to reprepare” after node restart
> on write workload in dtests, which we can avoid by using fully qualified cf
> names.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
