www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aled Sage (JIRA)" <j...@apache.org>
Subject [jira] [Created] (INFRA-8606) Incorrect `-Xmx26` in builds.apache.org, causing build failures
Date Tue, 11 Nov 2014 13:13:33 GMT
Aled Sage created INFRA-8606:

             Summary: Incorrect `-Xmx26` in builds.apache.org, causing build failures
                 Key: INFRA-8606
                 URL: https://issues.apache.org/jira/browse/INFRA-8606
             Project: Infrastructure
          Issue Type: Bug
          Components: Buildbot
            Reporter: Aled Sage
            Priority: Blocker

Many projects have failing maven builds due to an incorrect `-Xmx26` setting.

I see this error for deltaspike, brooklyn and cloudstack so presume it is a generic setting
that broke something within the last 24 hours.

e.g. from https://builds.apache.org/job/incubator-brooklyn-pull-requests/293/console:

[incubator-brooklyn-pull-requests] $ /home/jenkins/tools/java/latest1.6/bin/java -Xmx26 -Xms256m
-XX:MaxPermSize=512m -cp /home/jenkins/jenkins-slave/maven3-agent.jar:/home/jenkins/tools/maven/apache-maven-3.0.4/boot/plexus-classworlds-2.4.jar
org.jvnet.hudson.maven3.agent.Maven3Main /home/jenkins/tools/maven/apache-maven-3.0.4 /home/jenkins/jenkins-slave/slave.jar
/home/jenkins/jenkins-slave/maven3-interceptor.jar /home/jenkins/jenkins-slave/maven3-interceptor-commons.jar
Error occurred during initialization of VM
Incompatible minimum and maximum heap sizes specified
ERROR: Failed to launch Maven. Exit code = 1

This message was sent by Atlassian JIRA

View raw message