You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Daniel Takamori (JIRA)" <ji...@apache.org> on 2016/02/29 18:32:18 UTC

[jira] [Resolved] (INFRA-11313) JVM fails to allocate memory on Jenkins slave running on ubuntu-us1

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

Daniel Takamori resolved INFRA-11313.
-------------------------------------
    Resolution: Fixed

> JVM fails to allocate memory on Jenkins slave running on ubuntu-us1
> -------------------------------------------------------------------
>
>                 Key: INFRA-11313
>                 URL: https://issues.apache.org/jira/browse/INFRA-11313
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Jenkins
>         Environment: ubuntu-us1, latest JDK1.7
>            Reporter: Alex Rudyy
>            Assignee: Daniel Takamori
>         Attachments: hs_err_pid2809.log
>
>
> Jenkins job Qpid-Java-Java-BDB-6.0.x-TestMatrix running on ubuntu-us1 with latest JDK 1.7 failes to complete maven build due to failure to allocate memory
> {noformat}
> [INFO] 
> [INFO] --- maven-surefire-plugin:2.17:test (default-test) @ qpid-common ---
> [INFO] Surefire report directory: /home/jenkins/jenkins-slave/workspace/Qpid-Java-Java-BDB-6.0.x-TestMatrix/jdk/JDK 1.7 (latest)/label/Ubuntu/profile/java-bdb.0-10/common/target/surefire-reports
> Java HotSpot(TM) 64-Bit Server VM warning: INFO: os::commit_memory(0x00000007e8e00000, 267386880, 0) failed; error='Cannot allocate memory' (errno=12)
> #
> # There is insufficient memory for the Java Runtime Environment to continue.
> # Native memory allocation (malloc) failed to allocate 267386880 bytes for committing reserved memory.
> # An error report file with more information is saved as:
> # /home/jenkins/jenkins-slave/workspace/Qpid-Java-Java-BDB-6.0.x-TestMatrix/jdk/JDK 1.7 (latest)/label/Ubuntu/profile/java-bdb.0-10/hs_err_pid2809.log
> Build step 'Invoke top-level Maven targets' marked build as failure
> [locks-and-latches] Releasing all the locks
> [locks-and-latches] All the locks released
> Archiving artifacts
> Recording test results
> ERROR: Publisher 'Publish JUnit test result report' failed: No test report files were found. Configuration error?
> An attempt to send an e-mail to empty list of recipients, ignored.
> Finished: FAILURE
> {noformat}
> Here are logs from job startup identifying the problematic environment
> {noformat}
> Started by upstream project "Qpid-Java-Java-BDB-6.0.x-TestMatrix" build number 22
> originally caused by:
>  Started by user kwall
> [EnvInject] - Loading node environment variables.
> Building remotely on ubuntu-us1 (Ubuntu ubuntu ubuntu-us) in workspace /home/jenkins/jenkins-slave/workspace/Qpid-Java-Java-BDB-6.0.x-TestMatrix/jdk/JDK 1.7 (latest)/label/Ubuntu/profile/java-bdb.0-10
> Updating http://svn.apache.org/repos/asf/qpid/java/branches/6.0.x at revision '2016-02-23T08:49:53.085 +0000'
> Workspace appear to be locked, so getting a fresh workspace
> Cleaning local Directory .
> Checking out http://svn.apache.org/repos/asf/qpid/java/branches/6.0.x at revision '2016-02-23T08:49:53.085 +0000'
> {noformat}
> It looks like that issue similar to this one is reported in INFRA-11309. I raised a separate JIRA as it occurres on a different machine.



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