[
https://issues.apache.org/jira/browse/CASSANDRA-19960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885329#comment-17885329
]
Stefan Miklosovic commented on CASSANDRA-19960:
-----------------------------------------------
[CASSANDRA-19960-4.0|https://github.com/instaclustr/cassandra/tree/CASSANDRA-19960-4.0]
{noformat}
java11_separate_tests
✓ j11_build 1m 31s
✕ j11_jvm_dtests 13m 28s
org.apache.cassandra.distributed.test.RepairTest
testForcedNormalRepairWithOneNodeDown
✕ j11_unit_tests 8m 29s
org.apache.cassandra.net.ConnectionTest testTimeout
{noformat}
[java11_separate_tests|https://app.circleci.com/pipelines/github/instaclustr/cassandra/4835/workflows/ec4c3809-e6a5-4442-b3e5-d94b042b54c8]
> CommitLogArchiver in CommitLog should be final (19448 follow-up)
> ----------------------------------------------------------------
>
> Key: CASSANDRA-19960
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19960
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Commit Log
> Reporter: Stefan Miklosovic
> Assignee: Stefan Miklosovic
> Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0.x, 5.x
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> This is follow-up for CASSANDRA-19448, we made CommitLogArchiver non-final
> but not volatile. This might cause issues. We just need to return it back to
> final and remove the setter. The fact it is non-final now is because it was
> more comfortable to write tests but there is not any reason to keep it like
> that if tests are rewritten a little bit.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
