You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ekaterina Dimitrova (Jira)" <ji...@apache.org> on 2022/09/13 21:32:00 UTC
[jira] [Commented] (CASSANDRA-17889) Fix flaky test_archive_commitlog_point_in_time
[ https://issues.apache.org/jira/browse/CASSANDRA-17889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17603778#comment-17603778 ]
Ekaterina Dimitrova commented on CASSANDRA-17889:
-------------------------------------------------
Seems to me like a timing issue that I easily reproduced locally by reducing the timeout given to
_advance_to_next_cl_segment_ method. I. will experiment in CircleCI a bit
> Fix flaky test_archive_commitlog_point_in_time
> ----------------------------------------------
>
> Key: CASSANDRA-17889
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17889
> Project: Cassandra
> Issue Type: Bug
> Components: CI
> Reporter: Ekaterina Dimitrova
> Priority: Normal
> Fix For: 4.0.x, 4.1.x, 4.x
>
>
> Spotted in butler to fail for 4.0, 4.1 and trunk:
> h3.
> {code:java}
> Error Message
> AssertionError: It's been over a {s}s and we haven't written a new commitlog segment. Something is wrong.
> Stacktrace
> self = <snapshot_test.TestArchiveCommitlog object at 0x7efe72087d00> def test_archive_commitlog_point_in_time(self): """ Test archive commit log with restore_point_in_time setting """ > self.run_archive_commitlog(restore_point_in_time=True) snapshot_test.py:259: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ snapshot_test.py:301: in run_archive_commitlog advance_to_next_cl_segment( _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org