[jira] [Commented] (CASSANDRA-12415) dtest failure in replace_address_test.TestReplaceAddress.replace_stopped_node_test
[ https://issues.apache.org/jira/browse/CASSANDRA-12415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421517#comment-15421517 ] Jim Witschey commented on CASSANDRA-12415: -- Merged, closing. > dtest failure in > replace_address_test.TestReplaceAddress.replace_stopped_node_test > -- > > Key: CASSANDRA-12415 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12415 > Project: Cassandra > Issue Type: Test >Reporter: Philip Thompson >Assignee: Jim Witschey > Labels: blocked, dtest > > example failure: > http://cassci.datastax.com/job/cassandra-3.9_dtest/31/testReport/replace_address_test/TestReplaceAddress/replace_stopped_node_test > Node4 just doesn't start up in time. Maybe bump up the timeout, or move to > large test? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12415) dtest failure in replace_address_test.TestReplaceAddress.replace_stopped_node_test
[ https://issues.apache.org/jira/browse/CASSANDRA-12415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421488#comment-15421488 ] Jim Witschey commented on CASSANDRA-12415: -- Filed [this dtest PR|https://github.com/riptano/cassandra-dtest/pull/1238], which addresses the issue without dependencies: bq. This should have all the tests that I tagged as resource-intensive in #1212 run only on large instances. My mistake for thinking that actually skipping those should be blocked on other work. > dtest failure in > replace_address_test.TestReplaceAddress.replace_stopped_node_test > -- > > Key: CASSANDRA-12415 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12415 > Project: Cassandra > Issue Type: Test >Reporter: Philip Thompson >Assignee: Jim Witschey > Labels: blocked, dtest > > example failure: > http://cassci.datastax.com/job/cassandra-3.9_dtest/31/testReport/replace_address_test/TestReplaceAddress/replace_stopped_node_test > Node4 just doesn't start up in time. Maybe bump up the timeout, or move to > large test? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12415) dtest failure in replace_address_test.TestReplaceAddress.replace_stopped_node_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15418973#comment-15418973
]
Jim Witschey commented on CASSANDRA-12415:
--
Merged "move to larger instances" ticket here:
https://github.com/riptano/cassandra-dtest/pull/1212
Actually running this test on larger instances will start when we use
{{attrib}} for test exclusion, which I believe [~sean.mccarthy] is working on.
> dtest failure in
> replace_address_test.TestReplaceAddress.replace_stopped_node_test
> --
>
> Key: CASSANDRA-12415
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12415
> Project: Cassandra
> Issue Type: Test
>Reporter: Philip Thompson
>Assignee: Jim Witschey
> Labels: dtest
>
> example failure:
> http://cassci.datastax.com/job/cassandra-3.9_dtest/31/testReport/replace_address_test/TestReplaceAddress/replace_stopped_node_test
> Node4 just doesn't start up in time. Maybe bump up the timeout, or move to
> large test?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12415) dtest failure in replace_address_test.TestReplaceAddress.replace_stopped_node_test
[ https://issues.apache.org/jira/browse/CASSANDRA-12415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15415434#comment-15415434 ] Jim Witschey commented on CASSANDRA-12415: -- +1 to moving to larger instances. > dtest failure in > replace_address_test.TestReplaceAddress.replace_stopped_node_test > -- > > Key: CASSANDRA-12415 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12415 > Project: Cassandra > Issue Type: Test >Reporter: Philip Thompson >Assignee: DS Test Eng > Labels: dtest > > example failure: > http://cassci.datastax.com/job/cassandra-3.9_dtest/31/testReport/replace_address_test/TestReplaceAddress/replace_stopped_node_test > Node4 just doesn't start up in time. Maybe bump up the timeout, or move to > large test? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
