[ 
https://issues.apache.org/jira/browse/CASSANDRA-17232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17552030#comment-17552030
 ] 

Berenguer Blasi commented on CASSANDRA-17232:
---------------------------------------------

Note to self: we have 3 timeouts in circle atm which make sense as the patch 
will now be waiting for conditions to be met. If that translates into timeouts 
in jenkins we could always split the test in the future.

> org.apache.cassandra.db.commitlog.GroupCommitLogTest tests failing on trunk
> ---------------------------------------------------------------------------
>
>                 Key: CASSANDRA-17232
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17232
>             Project: Cassandra
>          Issue Type: Bug
>          Components: CI
>            Reporter: Ekaterina Dimitrova
>            Assignee: Berenguer Blasi
>            Priority: Normal
>             Fix For: 4.1-beta, 4.1.x, 4.x
>
>
> I saw 
> [here|https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1344/testReport/junit/org.apache.cassandra.db.commitlog/GroupCommitLogTest/replayWithDiscard_3_/]
>  and 
> [here|https://ci-cassandra.apache.org/job/Cassandra-trunk/881/testReport/junit/org.apache.cassandra.db.commitlog/GroupCommitLogTest/replayWithDiscard_3__compression_3/]
>  the same assertion failure:
>  
> {code:java}
> org.apache.cassandra.db.commitlog.GroupCommitLogTest.replayWithDiscard[3]
> Error Message
> expected:<204> but was:<0>
> Stacktrace
> junit.framework.AssertionFailedError: expected:<204> but was:<0> at 
> org.apache.cassandra.db.commitlog.CommitLogTest.replayWithDiscard(CommitLogTest.java:883)
> {code}
>  
> Then I find that there are many other tests from GroupCommitLogTest failing 
> with No such file found.
> Example:
> https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1344/



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to