You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Anthony Baker (JIRA)" <ji...@apache.org> on 2018/04/20 19:57:20 UTC

[jira] [Closed] (GEODE-1305) There are some tests that fail due to GC pauses. VMs need to be bounced more often in order to avoid this.

     [ https://issues.apache.org/jira/browse/GEODE-1305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anthony Baker closed GEODE-1305.
--------------------------------

> There are some tests that fail due to GC pauses. VMs need to be bounced more often in order to avoid this.
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-1305
>                 URL: https://issues.apache.org/jira/browse/GEODE-1305
>             Project: Geode
>          Issue Type: Bug
>          Components: build, tests
>            Reporter: Udo Kohlmeyer
>            Priority: Major
>
> Currently the DUnit tests fork every 30 test classes in order to avoid potential OOME or unnecessary GC pauses. Yet, unnecessary GCs still cause some tests to be marked as "flaky".
> In order reproduce this flaky behaviour, tests can be run until they fail. Which mostly occurs due to the test not cleaning up after itself.
> The "fork 30" functionality should be replicated in the test code, as running a single test/test class, eventually causes it to fail, due to GC issues.
> Ideally the VMs should be bounced after every test. But due to increased test times, this might be increased to bounce the VMs after a certain amount of tests rather the test classes as gradle script currently does.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)