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

Jay Zhuang commented on CASSANDRA-14610:
----------------------------------------

I'm unable to reproduce the problem locally, for the failed job in Jenkins, 
seems mostly it's because timeout to populate 6 nodes:
{noformat}
Error Message
ccmlib.node.NodeError: Error starting node1.
Stacktrace
self = <nodetool_test.TestNodetool object at 0x7ff1d3c26278>

    @since('4.0')
    def test_describecluster_more_information_three_datacenters(self):
        """
            nodetool describecluster should be more informative. It should 
include detailes
            for total node count, list of datacenters, RF, number of nodes per 
dc, how many
            are down and version(s).
            @jira_ticket CASSANDRA-13853
            @expected_result This test invokes nodetool describecluster and 
matches the output with the expected one
            """
        cluster = self.cluster
>       cluster.populate([2, 3, 1]).start(wait_for_binary_proto=True)
{noformat}

Other tests which requires 6 nodes all marked as 
{{@pytest.mark.resource_intensive}} (then these tests are skipped). I think 
reducing the node number from 6 to 4 should help.

+1 for the patch (also it passed 100 times locally run).

> Flaky dtest: 
> nodetool_test.TestNodetool.test_describecluster_more_information_three_datacenters
> -----------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-14610
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14610
>             Project: Cassandra
>          Issue Type: Task
>          Components: Testing, Tools
>            Reporter: Jason Brown
>            Assignee: Marcus Eriksson
>            Priority: Minor
>              Labels: dtest
>
> @jay zhuang observed 
> nodetool_test.TestNodetool.test_describecluster_more_information_three_datacenters
>  being flaky in Apache Jenkins. I ran locally and got a different flaky 
> behavior:
> {noformat}
>         out_node1_dc3, err, _ = node1_dc3.nodetool('describecluster')
>         assert 0 == len(err), err
> >       assert out_node1_dc1 == out_node1_dc3
> E       AssertionError: assert 'Cluster Info...1=3, dc3=1}\n' == 'Cluster 
> Infor...1=3, dc3=1}\n'
> E           Cluster Information:
> E             Name: test
> E             Snitch: org.apache.cassandra.locator.PropertyFileSnitch
> E             DynamicEndPointSnitch: enabled
> E             Partitioner: org.apache.cassandra.dht.Murmur3Partitioner
> E             Schema versions:
> E                     fc9ec7cd-80ba-3f27-87af-fc0bafcf7a03: [127.0.0.6, 
> 127.0.0.5, 127.0.0.4, 127.0.0.3, 127.0.0.2, 127.0.0.1]...
> E         
> E         ...Full output truncated (26 lines hidden), use '-vv' to show
> 09:58:14,357 ccm DEBUG Log-watching thread exiting.
> ===Flaky Test Report===
> test_describecluster_more_information_three_datacenters failed and was not 
> selected for rerun.
>       <class 'AssertionError'>
>       assert 'Cluster Info...1=3, dc3=1}\n' == 'Cluster Infor...1=3, dc3=1}\n'
>     Cluster Information:
>       Name: test
>       Snitch: org.apache.cassandra.locator.PropertyFileSnitch
>       DynamicEndPointSnitch: enabled
>       Partitioner: org.apache.cassandra.dht.Murmur3Partitioner
>       Schema versions:
>               fc9ec7cd-80ba-3f27-87af-fc0bafcf7a03: [127.0.0.6, 127.0.0.5, 
> 127.0.0.4, 127.0.0.3, 127.0.0.2, 127.0.0.1]...
>   
>   ...Full output truncated (26 lines hidden), use '-vv' to show
>       [<TracebackEntry 
> /opt/orig/1/opt/dev/cassandra-dtest/nodetool_test.py:373>]
> ===End Flaky Test Report===
> {noformat}
> As this test is for a patch that was introduced for 4.0, this dtest (should) 
> only be failing on trunk.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to