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

Ekaterina Dimitrova commented on CASSANDRA-16713:
-------------------------------------------------

Objects from SlidingTimeRate are created only in 3.11. I see failures for this 
test in Jenkins for 3.11 too so I think this will deserve some attention but it 
is not an urgent priority for 4.0 or a blocker

I suggest to comment out the test in 4.0 plus add a comment in SlidingTimeRate 
in case someone decides to use it at some point... Patch suggested 
[here|https://github.com/ekaterinadimitrova2/cassandra/commit/fa016965c0c1399d4f0ef497ce79ef43e83bd051]

Probably we can then close this ticket for 4.0 and open one for 3.11 to fix the 
test whoever has the time? Unfortunately, I won't have the time to dig into 
this problem now as part of this ticket. 

> Fix org.apache.cassandra.utils.SlidingTimeRateTest.testConcurrentUpdateAndGet
> -----------------------------------------------------------------------------
>
>                 Key: CASSANDRA-16713
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-16713
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Test/unit
>            Reporter: Ekaterina Dimitrova
>            Assignee: Ekaterina Dimitrova
>            Priority: Normal
>             Fix For: 4.0-rc2, 4.0, 3.11.x, 4.0.x
>
>
> Example failure:
> [https://ci-cassandra.apache.org/job/Cassandra-4.0/67/testReport/junit/org.apache.cassandra.utils/SlidingTimeRateTest/testConcurrentUpdateAndGet_cdc/]
> History of failing 3-4 times lately like that in Jenkins:
> https://jenkins-cm4.apache.org/job/Cassandra-4.0/76/testReport/junit/org.apache.cassandra.utils/SlidingTimeRateTest/testConcurrentUpdateAndGet_cdc/history/
>  



--
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