ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ivan Rakov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-8747) Remove\RemoveAll method should not count expired entry as removed.
Date Tue, 03 Jul 2018 16:22:00 GMT

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

Ivan Rakov commented on IGNITE-8747:
------------------------------------

Changes merged to master under IGNITE-8681.
Commit hash: a06c47f7e90005d342ab100270398e9c5ea5423d

> Remove\RemoveAll method should not count expired entry as removed.
> ------------------------------------------------------------------
>
>                 Key: IGNITE-8747
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8747
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>            Reporter: Andrew Mashenkov
>            Assignee: Andrew Mashenkov
>            Priority: Major
>              Labels: MakeTeamcityGreenAgain, tck, test-failure
>             Fix For: 2.7
>
>
> We have 2 TCK 1.0 test that are passed due to we have eagerTtl=true by default.
> The reason is remove() return true even if an expired entry was removed.
> Seems, we have to evict expired entry from cache on remove(), but do not count it as
removed.
> java.lang.AssertionError
>  at org.jsr107.tck.expiry.CacheExpiryTest.expire_whenAccessed(CacheExpiryTest.java:326)
> java.lang.AssertionError: expected:<0> but was:<1> at org.jsr107.tck.expiry.CacheExpiryTest.testCacheStatisticsRemoveAll(CacheExpiryTest.java:160)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message