You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltaspike.apache.org by "Gerhard Petracek (JIRA)" <ji...@apache.org> on 2016/11/24 16:38:58 UTC
[jira] [Commented] (DELTASPIKE-1225)
deltaspike.testcontrol.stop_container should stop the container after all
tests executed
[ https://issues.apache.org/jira/browse/DELTASPIKE-1225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15693712#comment-15693712 ]
Gerhard Petracek commented on DELTASPIKE-1225:
----------------------------------------------
you are very welcome to provide a patch which is compatible with junit v4.10+, otherwise you have to handle it on your own in the build-script by using:
{code}
CdiContainerLoader.getCdiContainer().shutdown();
{code}
at the point which is appropriate for your setup.
> deltaspike.testcontrol.stop_container should stop the container after all tests executed
> ----------------------------------------------------------------------------------------
>
> Key: DELTASPIKE-1225
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1225
> Project: DeltaSpike
> Issue Type: Bug
> Components: TestControl
> Affects Versions: 1.7.2
> Reporter: Remo
>
> deltaspike.testcontrol.stop_container is very useful to speed up test cases. However, it results that the container does not getting shutdown at all. This should still be done after ALL the tests have been executed.
> With Gradle the current behavior is quite a problem. The Gradle Wrappers keep by default the VM running. And as such, test cases must properly cleanup and free resources. Otherwise the Gradle wrapper consumes more and more memory and dies at some point.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)