[
https://issues.apache.org/jira/browse/CASSANDRA-10166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14743086#comment-14743086
]
Sylvain Lebresne commented on CASSANDRA-10166:
----------------------------------------------
Actually, I'm re-putting this on RC1. This ticket has always been meant as a
placeholder for fixing all our utests/dtests before release, and me not having
taken the time to open ticket for all the failures we have is not a good
indication of the progress towards that goal. In fact, our dtests are still far
from 0 failures and from the history of such dtests it seems the current trend
is towards more failures rather than less. And it does feels to me that dealing
with all the tests we do have should be a strong requirement for calling
something a "release candidate".
> Failing tests on cassandra 3.0 branch
> -------------------------------------
>
> Key: CASSANDRA-10166
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10166
> Project: Cassandra
> Issue Type: Test
> Reporter: Sylvain Lebresne
> Fix For: 3.0.0 rc1
>
>
> Until we find a better way to track those things, this is meant as a master
> ticket to track tickets open regarding tests (unit test and dtests, though at
> the time of this writing only dtest are still failing) that are still
> failing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
