You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Philip Thompson (JIRA)" <ji...@apache.org> on 2016/03/10 20:44:40 UTC
[jira] [Commented] (CASSANDRA-11227) dtest failure in
replication_test.SnitchConfigurationUpdateTest.test_failed_snitch_update_property_file_snitch
[ https://issues.apache.org/jira/browse/CASSANDRA-11227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15189839#comment-15189839 ]
Philip Thompson commented on CASSANDRA-11227:
---------------------------------------------
The real problem is that only two nodes are up, when we launched 3.
> dtest failure in replication_test.SnitchConfigurationUpdateTest.test_failed_snitch_update_property_file_snitch
> --------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-11227
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11227
> Project: Cassandra
> Issue Type: Test
> Reporter: Russ Hatch
> Assignee: Philip Thompson
> Labels: dtest
>
> example failure:
> http://cassci.datastax.com/job/cassandra-2.1_offheap_dtest/301/testReport/replication_test/SnitchConfigurationUpdateTest/test_failed_snitch_update_property_file_snitch
> Failed on CassCI build cassandra-2.1_offheap_dtest #301
> Failed on CassCI build cassandra-2.1_offheap_dtest #286
> Looks to be a timeout issue on both historical failures:
> {noformat}
> Ran out of time waiting for topology to change on node 0
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)