-
Task
-
Resolution: Done
-
Blocker
Tests on the 2.0 branch require crazy amounts of RAM or that the VM be killed after every test. This appears to be a regression from 1.x.
Running the full test suite (on 2.0, Maven 3.3.3 and Java 8):
Surefire forked booter 1:
Surefire forked booter 2 (there is a little jconsole disconnection of ~4 minutes in my local env, but nothing remarkable happened in the middle):
Maven launcher process:
Running the full test suite (on 2.0, Maven 3.3.3 and Java 7 and -Xmx600m - lowered from the current value of -Xmx1g):
Surefire forked booter 1:
Surefire forked booter 2:
Maven launcher process:
Running the full test suite (on 1.x, Maven 3.3.3 and Java 7 and -Xmx256):
Surefire forked booter 1:
Surefire forked booter 2:
Maven launcher process:
[JENKINS-33809] Find out what's wrong with the tests on the 2.0 branch requiring so much RAM
| Epic Link |
New:
|
| Rank | New: Ranked higher |
Spike Washburn
made changes -
| Assignee | New: Antonio Muñiz [ amuniz ] |
| Labels | Original: 2.0 2.0-beta regression | New: 2.0 2.0-beta 2.0-planned regression |
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
| Attachment | New: jenkins2-surefire-booter.png [ 32294 ] | |
| Attachment | New: jenkins2-maven-launcher.png [ 32295 ] | |
| Attachment | New: jenkins1-surefire-booter.png [ 32296 ] | |
| Attachment | New: jenkins1-maven-launcher.png [ 32297 ] |
| Description | Original: Tests on the 2.0 branch require crazy amounts of RAM or that the VM be killed after every test. This appears to be a regression from 1.x. |
New:
Tests on the 2.0 branch require crazy amounts of RAM or that the VM be killed after every test. This appears to be a regression from 1.x. Monitor of Jenkins 1.x (JDKInstallerTest run): 1. Maven launcher process: !jenkins1-maven-launcher.png|thumbnail! 2. Surefire booter: !jenkins1-surefire-booter.png|thumbnail! Monitor of Jenkins 2.x (JDKInstallerTest run): 1. Maven launcher process !jenkins2-maven-launcher.png|thumbnail! 2. Surefire booter !jenkins2-surefire-booter.png|thumbnail! |
| Description |
Original:
Tests on the 2.0 branch require crazy amounts of RAM or that the VM be killed after every test. This appears to be a regression from 1.x. Monitor of Jenkins 1.x (JDKInstallerTest run): 1. Maven launcher process: !jenkins1-maven-launcher.png|thumbnail! 2. Surefire booter: !jenkins1-surefire-booter.png|thumbnail! Monitor of Jenkins 2.x (JDKInstallerTest run): 1. Maven launcher process !jenkins2-maven-launcher.png|thumbnail! 2. Surefire booter !jenkins2-surefire-booter.png|thumbnail! |
New:
Tests on the 2.0 branch require crazy amounts of RAM or that the VM be killed after every test. This appears to be a regression from 1.x. Monitor of Jenkins 1.x (JDKInstallerTest run): 1. Maven launcher process: !jenkins1-maven-launcher.png|width=200,height=200! 2. Surefire booter: !jenkins1-surefire-booter.png|thumbnail! Monitor of Jenkins 2.x (JDKInstallerTest run): 1. Maven launcher process !jenkins2-maven-launcher.png|thumbnail! 2. Surefire booter !jenkins2-surefire-booter.png|thumbnail! |
It's visible in attached screenshots that the major difference on used RAM is on Maven launcher process, not surefire booter. Investigating why...