cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Witschey (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (CASSANDRA-11394) dtest failure in upgrade_tests.upgrade_through_versions_test.ProtoV1Upgrade_2_1_UpTo_2_2_HEAD.bootstrap_multidc_test
Date Fri, 25 Mar 2016 15:51:25 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-11394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jim Witschey reassigned CASSANDRA-11394:
----------------------------------------

    Assignee: Jim Witschey  (was: DS Test Eng)

> dtest failure in upgrade_tests.upgrade_through_versions_test.ProtoV1Upgrade_2_1_UpTo_2_2_HEAD.bootstrap_multidc_test
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-11394
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11394
>             Project: Cassandra
>          Issue Type: Test
>          Components: Testing
>            Reporter: Philip Thompson
>            Assignee: Jim Witschey
>              Labels: dtest
>         Attachments: node1.log, node1_debug.log, node2.log, node2_debug.log, node3.log,
node3_debug.log, node4.log, node4_debug.log, node5.log, node5_debug.log
>
>
> The other nodes fail to notice node5 come up. If we check the logs, they're complaining
about long interval times for that node. Might just be an issue with how many nodes we're
starting? I don't actually see any errors.
> Logs for this failure attached. This is flaky, and has happened on a few bootstrap_multidc_tests
> example failure:
> http://cassci.datastax.com/job/upgrade_tests-all/24/testReport/upgrade_tests.upgrade_through_versions_test/ProtoV1Upgrade_2_1_UpTo_2_2_HEAD/bootstrap_multidc_test
> Failed on CassCI build upgrade_tests-all #24



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message