[ 
https://issues.apache.org/jira/browse/CASSANDRA-15977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17214624#comment-17214624
 ] 

Andres de la Peña commented on CASSANDRA-15977:
-----------------------------------------------

[~jmckenzie] Indeed, I've rebased the branches and running CI, I'll post the 
results once it's finished.

Also, as [discussed in 
Slack|https://the-asf.slack.com/archives/CK23JSY2K/p1602182196170300?thread_ts=1602111667.128800&cid=CK23JSY2K],
 I'm adding a new {{@ported_to_in_jvm}} Python marker for dtests, so they are 
only skipped without vnodes, and they are easy to identify when/if we add 
support for virtual nodes in-JVM.

> 4.0 quality testing: Read Repair
> --------------------------------
>
>                 Key: CASSANDRA-15977
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-15977
>             Project: Cassandra
>          Issue Type: Task
>          Components: Test/dtest/java, Test/unit
>            Reporter: Andres de la Peña
>            Assignee: Andres de la Peña
>            Priority: Normal
>             Fix For: 4.0-beta
>
>          Time Spent: 13h 20m
>  Remaining Estimate: 0h
>
> This is a subtask of CASSANDRA-15579 focusing on read repair.
> [This 
> document|https://docs.google.com/document/d/1-gldHcdLSMRbDhhI8ahs_tPeAZsjurjXr38xABVjWHE/edit?usp=sharing]
>  lists and describes the existing functional tests for read repair, so we can 
> have a broad view of what is currently covered. We can comment on this 
> document and add ideas for new cases/tests, so it can gradually evolve to a 
> more or less detailed test plan.



--
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

Reply via email to