You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Stefan Egli (JIRA)" <ji...@apache.org> on 2015/11/10 09:34:10 UTC

[jira] [Resolved] (SLING-5287) OOME with DiscoveryServiceImplTest.testThirtyInstances on jenkins

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

Stefan Egli resolved SLING-5287.
--------------------------------
    Resolution: Fixed

reduced the 'thirty' test to be a 'twenty-four' in rev 1713588 - perhaps that's enough.

> OOME with DiscoveryServiceImplTest.testThirtyInstances on jenkins
> -----------------------------------------------------------------
>
>                 Key: SLING-5287
>                 URL: https://issues.apache.org/jira/browse/SLING-5287
>             Project: Sling
>          Issue Type: Test
>          Components: Extensions
>    Affects Versions: Discovery Impl 1.2.0, Discovery Base 1.0.2
>            Reporter: Stefan Egli
>            Assignee: Stefan Egli
>             Fix For: Discovery Impl 1.2.2, Discovery Base 1.1.0
>
>
> As noted on the [mailinglist|http://markmail.org/message/ksdc4jdmyd2fk5nn] there are OOME happening on jenkins - mostly during DiscoveryServiceImplTest.testThirtyInstances.
> Either we increase the memory or change this test.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)