You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Nikolai Kulagin (Jira)" <ji...@apache.org> on 2019/10/21 18:35:00 UTC
[jira] [Commented] (IGNITE-9005) Eviction policy MBeans change
failed LifecycleAwareTest on cache name injectoin
[ https://issues.apache.org/jira/browse/IGNITE-9005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16956367#comment-16956367 ]
Nikolai Kulagin commented on IGNITE-9005:
-----------------------------------------
[~slukyanov], hello. I copied your fix to my branch and fixed the errors ([PR|https://github.com/apache/ignite/pull/6970]). Can this speed up the task? Or maybe I can take on the task?
> Eviction policy MBeans change failed LifecycleAwareTest on cache name injectoin
> -------------------------------------------------------------------------------
>
> Key: IGNITE-9005
> URL: https://issues.apache.org/jira/browse/IGNITE-9005
> Project: Ignite
> Issue Type: Bug
> Reporter: Dmitry Pavlov
> Assignee: Stanislav Lukyanov
> Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> http://apache-ignite-developers.2346864.n4.nabble.com/MTCGA-new-failures-in-builds-1485687-needs-to-be-handled-td32531.html
> New test failure detected https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=7246907407546697403&branch=%3Cdefault%3E&tab=testDetails
> after merging
> IGNITE-8776 Eviction policy MBeans are never registered if evictionPolicyFactory is used
> Revert of commit makes test passing.
> Locally test also failed. Failed with message
> {noformat}
> Unexpected cache name for org.apache.ignite.internal.processors.cache.GridCacheLifecycleAwareSelfTest$TestEvictionPolicy@322714f4 expected:<cache> but was:<null>
> {noformat}
> Message of failure seems to be related to TestEvictionPolicy instance from test class.
> Seems that returing call to cctx.kernalContext (). resource (). injectCacheName (rsrc, cfg.getName ()); should fix issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)