[
https://issues.apache.org/jira/browse/IGNITE-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15142459#comment-15142459
]
Vladimir Ershov commented on IGNITE-2565:
-----------------------------------------
I've take a look on some of that typical issues and it looks like they are
actually not typical and have different reasons. The last one:
{noformat}
java.lang.AssertionError: expected:<0> but was:<1>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:743)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at
org.jsr107.tck.management.CacheMBStatisticsBeanTest.testCacheStatistics(CacheMBStatisticsBeanTest.java:104)
{noformat}
Most likely to be related with counting miss logic on the server side, which is
not linked to IGNITE-2483, and should be fixed at separated ticket.
> TCK suite fail periodically
> ---------------------------
>
> Key: IGNITE-2565
> URL: https://issues.apache.org/jira/browse/IGNITE-2565
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 1.5.0.final
> Reporter: Anton Vinogradov
> Assignee: Vladimir Ershov
> Priority: Critical
> Labels: important
> Fix For: 1.6
>
>
> TCK suite fail periodically fails with assetrions about CacheHitPercentage.
> I see that a lot of changes was made last two months where added logic with
> invoking of metrics.onRead(); possible this affects statictic counting.
> Typical stacktrace:
> java.lang.AssertionError: expected:<100.0> but was:<50.0>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:743)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:144)
> at
> org.jsr107.tck.management.CacheMBStatisticsBeanTest.testCacheStatisticsInvokeEntryProcessorRemove(CacheMBStatisticsBeanTest.java:424)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
