[
https://issues.apache.org/jira/browse/IGNITE-8110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433999#comment-16433999
]
Anton Kurbanov commented on IGNITE-8110:
----------------------------------------
[~dpavlov], looks like this test is unrelated. Only affected functionality is
write-behind cache, also found several failures in test's history. On my local
machine this test in suite runs fine.
Failed tests are also different on separate runs for my branch:
RunAll execution, these test succeeded:
[https://ci.ignite.apache.org/viewLog.html?buildId=1176364&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_Cache2]
Separate Cache tests execution where they failed:
[https://ci.ignite.apache.org/viewLog.html?buildId=1177272&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_Cache2]
> GridCacheWriteBehindStore.Flusher thread uses the wrong transformation from
> milliseconds to nanoseconds.
> --------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-8110
> URL: https://issues.apache.org/jira/browse/IGNITE-8110
> Project: Ignite
> Issue Type: Bug
> Components: general
> Affects Versions: 2.4
> Reporter: Vyacheslav Koptilin
> Assignee: Anton Kurbanov
> Priority: Minor
> Fix For: 2.6
>
>
> The initial value of a cache flushing frequency is defined as follows:
> {code}
> /** Cache flushing frequence in nanos. */
> protected long cacheFlushFreqNanos = cacheFlushFreq * 1000;
> {code}
> where is {{cacheFlushFreq}} is equal to
> {code}
> /** Default flush frequency for write-behind cache store in milliseconds.
> */
> public static final long DFLT_WRITE_BEHIND_FLUSH_FREQUENCY = 5000;
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
