[
https://issues.apache.org/jira/browse/IGNITE-10820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729853#comment-16729853
]
Ignite TC Bot commented on IGNITE-10820:
----------------------------------------
{panel:title=--> Run :: All: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2654426&buildTypeId=IgniteTests24Java8_RunAll]
> Clean up static Ignite instances in tests
> -----------------------------------------
>
> Key: IGNITE-10820
> URL: https://issues.apache.org/jira/browse/IGNITE-10820
> Project: Ignite
> Issue Type: Improvement
> Reporter: Alexey Goncharuk
> Assignee: Alexey Goncharuk
> Priority: Major
> Fix For: 2.8
>
>
> From the recent TC OOME it can be seen that some tests contain static Ignite
> instances that are not cleaned up on test end, which leads to memory leak. As
> a first phase, we need to nullify them. Ultimately, we need to get rid of
> static fields in tests after migration to JUnit5.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
