infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zoran Regvart (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (INFRA-14350) Getting OutOfMemory errors on Jenkins builds
Date Wed, 14 Jun 2017 08:09:00 GMT

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

Zoran Regvart updated INFRA-14350:
----------------------------------
    Description: 
Building Apache Camel jobs on Jenkins fails with OutOfMemory issues, I think they are caused
by using Maven job type combined with great number of Maven modules.
See https://builds.apache.org/view/A-D/view/Camel/job/Camel.trunk.fulltest.java9/469/console
for instance.
I think this causes cascading failures of other jobs run at the same time manifested as ChannelClosedException
(see https://builds.apache.org/view/A-D/view/Camel/job/Camel.trunk.fulltest.java8/1428/console.

Can the node memory be increased?

  was:
Building Apache Camel jobs on Jenkins fails with OutOfMemory issues, I think they are caused
by using Maven job type combined with great number of Maven modules.
See [Camel.trunk.fulltest.java9/469/console|https://builds.apache.org/view/A-D/view/Camel/job/Camel.trunk.fulltest.java9/469/console]
for instance.
I think this causes cascading failures of other jobs run at the same time manifested as ChannelClosedException
(see [Camel.trunk.fulltest.java8/1428/console|https://builds.apache.org/view/A-D/view/Camel/job/Camel.trunk.fulltest.java8/1428/console].

Can the node memory be increased?


> Getting OutOfMemory errors on Jenkins builds
> --------------------------------------------
>
>                 Key: INFRA-14350
>                 URL: https://issues.apache.org/jira/browse/INFRA-14350
>             Project: Infrastructure
>          Issue Type: Improvement
>          Components: Jenkins
>            Reporter: Zoran Regvart
>
> Building Apache Camel jobs on Jenkins fails with OutOfMemory issues, I think they are
caused by using Maven job type combined with great number of Maven modules.
> See https://builds.apache.org/view/A-D/view/Camel/job/Camel.trunk.fulltest.java9/469/console
for instance.
> I think this causes cascading failures of other jobs run at the same time manifested
as ChannelClosedException (see https://builds.apache.org/view/A-D/view/Camel/job/Camel.trunk.fulltest.java8/1428/console.
> Can the node memory be increased?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message