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

David Capwell commented on CASSANDRA-15676:
-------------------------------------------

I will file a different but related JIRA, CASSANDRA-15650 broke this test and 
causing it to hang consistently.  I checked the original build and see it 
didn't have CASSANDRA-15650, so the timeout happened before CASSANDRA-15650, 
but now consistent with CASSANDRA-15650.

> flaky test testWriteUnknownResult- 
> org.apache.cassandra.distributed.test.CasWriteTest
> -------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-15676
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-15676
>             Project: Cassandra
>          Issue Type: Task
>          Components: Test/dtest
>            Reporter: Kevin Gallardo
>            Assignee: Eduard Tudenhoefner
>            Priority: Normal
>             Fix For: 4.0-beta
>
>
> Failure observed in: 
> https://app.circleci.com/pipelines/github/newkek/cassandra/33/workflows/54007cf7-4424-4ec1-9655-665f6044e6d1/jobs/187/tests
> {noformat}
> testWriteUnknownResult - org.apache.cassandra.distributed.test.CasWriteTest
> junit.framework.AssertionFailedError: Expecting cause to be 
> CasWriteUncertainException
>       at 
> org.apache.cassandra.distributed.test.CasWriteTest.testWriteUnknownResult(CasWriteTest.java:257)
>       at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>       at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>       at 
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> {noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Reply via email to