[ https://issues.apache.org/jira/browse/CASSANDRA-14597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16576632#comment-16576632 ]
Jason Brown commented on CASSANDRA-14597: ----------------------------------------- +1 on this solution. We could, alternatively, set the timeout only on the call to [advance_to_next_cl_segment in TestCommitlogArchive.run_archive_commitlog()|https://github.com/riptano/cassandra-dtest/blob/master/snapshot_test.py#L252], rather than change the default for the function in hacks.py. Either way is fine with me, let's just get this one knocked out. Thanks for looking into this one, [~spo...@gmail.com]. > [dtest] snapshot_test.TestArchiveCommitlog > ------------------------------------------ > > Key: CASSANDRA-14597 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14597 > Project: Cassandra > Issue Type: Bug > Reporter: Jason Brown > Priority: Minor > Labels: dtest > Attachments: 2_2.txt, 3_0.txt, 3_11_3.txt > > > All TestArchiveCommitLog dtests fail on 3.0, but no other branches. Output > from pytest error: > {noformat} > assert ( > time.time() <= stop_time), "It's been over a {s}s and we > haven't written a new " + \ > > "commitlog segment. Something is wrong.".format(s=timeout) > E AssertionError: It's been over a {s}s and we haven't written a > new commitlog segment. Something is wrong. > tools/hacks.py:61: AssertionError > {noformat} -- 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