[
https://issues.apache.org/jira/browse/CASSANDRA-19100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17856553#comment-17856553
]
Stefan Miklosovic commented on CASSANDRA-19100:
-----------------------------------------------
If sleeping fixes it and multiplexer passes I think we are just good to go.
Maybe even increasing the sleep to be extra sure this won't occur again?
Finding ourselves in a situation when 1s sleep is not enough would be a bummer.
Otherwise +1
> commitlog_test.py::TestCommitLog::test_stop_failure_policy failed
> -----------------------------------------------------------------
>
> Key: CASSANDRA-19100
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19100
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
> Reporter: Jacek Lewandowski
> Assignee: Brandon Williams
> Priority: Normal
> Fix For: 5.0-rc, 5.x
>
>
> https://app.circleci.com/pipelines/github/jacek-lewandowski/cassandra/1121/workflows/fce907b1-0526-4d4d-beb5-b6620737a5f3/jobs/50905/tests
> {noformat}
> AssertionError: Cannot find the commitlog failure message in logs
> assert []
> self = <commitlog_test.TestCommitLog object at 0x7f1bf1cb3f50>
> def test_stop_failure_policy(self):
> """
> Test the stop commitlog failure policy (default one)
> """
> self.prepare()
>
> self._provoke_commitlog_failure()
> failure = self.node1.grep_log("Failed .+ commit log segments. Commit
> disk failure policy is stop; terminating thread")
> logger.debug(failure)
> > assert failure, "Cannot find the commitlog failure message in logs"
> E AssertionError: Cannot find the commitlog failure message in logs
> E assert []
> commitlog_test.py:325: AssertionError
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
