[RELENG-18] Maven JVM terminated unexpectedly with exit code 137 Created: 11/Jun/15 Updated: 19/Oct/17 Resolved: 14/Jun/15 |
|
| Status: | Resolved |
| Project: | releng |
| Component/s: | Autorelease |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Thanh Ha (zxiiro) | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 3679 |
| Description |
|
According to my Googling this code means that Maven is running out of JVM memory. The solution might be to increase the memory. Considering that Build slaves launch with 8GB total we will try bumping the build memory from 4G to 6G. Proposed patch: https://git.opendaylight.org/gerrit/22400 |
| Comments |
| Comment by Thanh Ha (zxiiro) [ 14/Jun/15 ] |
|
Additionally we needed to upgrade our Rackspace Slave VM. The solution ended up being to switch to the io1-15 VM and created a separate Jenkins node called dynamic_autorelease for autorelease builds. Additional spinup script produced: https://git.opendaylight.org/gerrit/22541 Finally successfully produced a build with: https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-lithium/24/ |