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/23 18:54:25 UTC
[jira] [Resolved] (CASSANDRA-11318) dtest failure in
replication_test.SnitchConfigurationUpdateTest.test_rf_collapse_property_file_snitch
[ https://issues.apache.org/jira/browse/CASSANDRA-11318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Philip Thompson resolved CASSANDRA-11318.
-----------------------------------------
Resolution: Cannot Reproduce
Did not show up in 300 separate runs:
http://cassci.datastax.com/view/Parameterized/job/parameterized_dtest_multiplexer/34/
Closing as Cannot Repro.
> dtest failure in replication_test.SnitchConfigurationUpdateTest.test_rf_collapse_property_file_snitch
> -----------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-11318
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11318
> Project: Cassandra
> Issue Type: Test
> Reporter: Jim Witschey
> Assignee: Philip Thompson
> Labels: dtest
>
> example failure:
> http://cassci.datastax.com/job/cassandra-3.0_dtest/592/testReport/replication_test/SnitchConfigurationUpdateTest/test_rf_collapse_property_file_snitch
> Failed on CassCI build cassandra-3.0_dtest #592
> The test failed on this line:
> https://github.com/riptano/cassandra-dtest/blob/7a331cda807c96ae107b58017854f0e57996d8c3/replication_test.py#L567
> So, a node's expected move from one rack to another doesn't happen in the allotted timeout time. This is the only flap I've seen. Maybe the thing to do here is increase the timeout and keep an eye on it?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)