[
https://issues.apache.org/jira/browse/CASSANDRA-14597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16563537#comment-16563537
]
Stefan Podkowinski edited comment on CASSANDRA-14597 at 7/31/18 12:36 PM:
--------------------------------------------------------------------------
Looks like the test itself works fine, but the segment allocation behaviour is
changed across different versions and 3.0 doesn't allocate a new segment within
the timeout to make the test pass.
was (Author: spo...@gmail.com):
Looks like the test itself works fine, but the log allocation behaviour is
changed across different versions and 3.0 doesn't allocate a new log to make
the test pass.
> [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
