[
https://issues.apache.org/jira/browse/IGNITE-10820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728963#comment-16728963
]
ASF GitHub Bot commented on IGNITE-10820:
-----------------------------------------
GitHub user agoncharuk opened a pull request:
https://github.com/apache/ignite/pull/5752
IGNITE-10820 Nullify static Ignite fields in tests
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10820
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5752.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #5752
----
commit 26b15e874bbc73d4986034dd378214f6774accb8
Author: Alexey Goncharuk <alexey.goncharuk@...>
Date: 2018-12-26T09:57:43Z
IGNITE-10820 Nullify static Ignite fields in tests
----
> 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)
