You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2013/11/17 05:11:20 UTC

[jira] [Comment Edited] (CASSANDRA-6365) Bisect unit test failures on 2.0 branch

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

Jonathan Ellis edited comment on CASSANDRA-6365 at 11/17/13 4:10 AM:
---------------------------------------------------------------------

01a57eea841e51fb4a97329ab9fa0f59d0b826f6 passes for me too :-| [Edit: twice in a row]

My takeaway is we've had heisenbugs for a while but at some point we introduced some that reproduce more readily because 2.0 HEAD hasn't passed in a long time.


was (Author: jbellis):
01a57eea841e51fb4a97329ab9fa0f59d0b826f6 passes for me too :-|

My takeaway is we've had heisenbugs for a while but at some point we introduced some that reproduce more readily because 2.0 HEAD hasn't passed in a long time.

> Bisect unit test failures on 2.0 branch
> ---------------------------------------
>
>                 Key: CASSANDRA-6365
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6365
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tests
>            Reporter: Jonathan Ellis
>            Assignee: Michael Shuler
>         Attachments: 2.0.1-utest.txt, C-2.0.1_tag_utests.txt
>
>
> Unit tests pass in 2.0.1.
> They do not in 2.0.2.
> Let's find where the failures were introduced.



--
This message was sent by Atlassian JIRA
(v6.1#6144)