You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Kovalenko (JIRA)" <ji...@apache.org> on 2018/02/19 16:06:00 UTC
[jira] [Assigned] (IGNITE-7750) testMultiThreadStatisticsEnable is
flaky on TC
[ https://issues.apache.org/jira/browse/IGNITE-7750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pavel Kovalenko reassigned IGNITE-7750:
---------------------------------------
Assignee: Alexey Goncharuk (was: Pavel Kovalenko)
Affects Version/s: 2.5
Fix is ready.
Changes are tiny and only in test.
TC (Suite contains this test): https://ci.ignite.apache.org/viewLog.html?buildId=1100809&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_IgniteCache3
PR: https://github.com/apache/ignite/pull/3541
> testMultiThreadStatisticsEnable is flaky on TC
> ----------------------------------------------
>
> Key: IGNITE-7750
> URL: https://issues.apache.org/jira/browse/IGNITE-7750
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 2.5
> Reporter: Pavel Kovalenko
> Assignee: Alexey Goncharuk
> Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.5
>
>
> {code:java}
> class org.apache.ignite.IgniteException: Cache not found [cacheName=cache2]
> at org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:985)
> at org.apache.ignite.internal.cluster.IgniteClusterImpl.enableStatistics(IgniteClusterImpl.java:497)
> at org.apache.ignite.internal.processors.cache.CacheMetricsEnableRuntimeTest$3.run(CacheMetricsEnableRuntimeTest.java:181)
> at org.apache.ignite.testframework.GridTestUtils$9.call(GridTestUtils.java:1275)
> at org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
> Caused by: class org.apache.ignite.IgniteCheckedException: Cache not found [cacheName=cache2]
> at org.apache.ignite.internal.processors.cache.GridCacheProcessor.enableStatistics(GridCacheProcessor.java:4227)
> at org.apache.ignite.internal.cluster.IgniteClusterImpl.enableStatistics(IgniteClusterImpl.java:494)
> ... 3 more
> {code}
> The problem of the test:
> 1) We don't wait for exchange future completion after "cache2" is started and it may lead to NullPointerException when we try to obtain reference to "cache2" on the node which doesn't complete exchange future and initialize cache proxy.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)