Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-33809

Find out what's wrong with the tests on the 2.0 branch requiring so much RAM

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      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:

        Attachments

        1. forked-booter-1.png
          forked-booter-1.png
          354 kB
        2. forked-booter-2.png
          forked-booter-2.png
          331 kB
        3. java7-1.x-maven-launcher.png
          java7-1.x-maven-launcher.png
          20 kB
        4. java7-1.x-surefire-booter1.png
          java7-1.x-surefire-booter1.png
          56 kB
        5. java7-1.x-surefire-booter2.png
          java7-1.x-surefire-booter2.png
          50 kB
        6. java7-2.0-maven-launcher.png
          java7-2.0-maven-launcher.png
          21 kB
        7. java7-2.0-surefire-booter1.png
          java7-2.0-surefire-booter1.png
          70 kB
        8. java7-2.0-surefire-booter2.png
          java7-2.0-surefire-booter2.png
          75 kB
        9. jenkins1-maven-launcher.png
          jenkins1-maven-launcher.png
          253 kB
        10. jenkins1-surefire-booter.png
          jenkins1-surefire-booter.png
          261 kB
        11. jenkins2-maven-launcher.png
          jenkins2-maven-launcher.png
          230 kB
        12. jenkins2-surefire-booter.png
          jenkins2-surefire-booter.png
          259 kB
        13. maven-laucher.png
          maven-laucher.png
          152 kB

          Activity

          danielbeck Daniel Beck created issue -
          danielbeck Daniel Beck made changes -
          Field Original Value New Value
          Epic Link JENKINS-33810 [ 169285 ]
          danielbeck Daniel Beck made changes -
          Rank Ranked higher
          swashbuck1r Spike Washburn made changes -
          Assignee Antonio Muñiz [ amuniz ]
          danielbeck Daniel Beck made changes -
          Labels 2.0 2.0-beta regression 2.0 2.0-beta 2.0-planned regression
          amuniz Antonio Muñiz made changes -
          Status Open [ 1 ] In Progress [ 3 ]
          amuniz Antonio Muñiz made changes -
          Attachment jenkins2-surefire-booter.png [ 32294 ]
          Attachment jenkins2-maven-launcher.png [ 32295 ]
          Attachment jenkins1-surefire-booter.png [ 32296 ]
          Attachment jenkins1-maven-launcher.png [ 32297 ]
          amuniz Antonio Muñiz made changes -
          Description 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. 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!
          amuniz Antonio Muñiz made changes -
          Description 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!
          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!
          amuniz Antonio Muñiz made changes -
          Description 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!
          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=400,height=300!

          2. Surefire booter:

          !jenkins1-surefire-booter.png|width=400,height=300!

          Monitor of Jenkins 2.x (JDKInstallerTest run):

          1. Maven launcher process

          !jenkins2-maven-launcher.png|width=400,height=300!

          2. Surefire booter

          !jenkins2-surefire-booter.png|width=400,height=300!
          amuniz Antonio Muñiz made changes -
          Attachment maven-laucher.png [ 32299 ]
          Attachment forked-booter-2.png [ 32300 ]
          Attachment forked-booter-1.png [ 32301 ]
          amuniz Antonio Muñiz made changes -
          Description 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=400,height=300!

          2. Surefire booter:

          !jenkins1-surefire-booter.png|width=400,height=300!

          Monitor of Jenkins 2.x (JDKInstallerTest run):

          1. Maven launcher process

          !jenkins2-maven-launcher.png|width=400,height=300!

          2. Surefire booter

          !jenkins2-surefire-booter.png|width=400,height=300!
          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.

          h3. Jenkins 1.x vs. 2.0 comparison running a single test ({{JDKInstallerTest}})

          h4. Jenkins 1.x

          1. Maven launcher process:

          !jenkins1-maven-launcher.png|width=400,height=300!

          2. Surefire booter:

          !jenkins1-surefire-booter.png|width=400,height=300!

          h4. Jenkins 2.0

          1. Maven launcher process

          !jenkins2-maven-launcher.png|width=400,height=300!

          2. Surefire booter

          !jenkins2-surefire-booter.png|width=400,height=300!

          h3. Running the full test suite (on 2.0, Maven 3.3.3 and Java 8):

          Surefire forked booter 1:

          !forked-booter-1.png|width=550,height=300!

          Surefire forked booter 2:

          !forked-booter-2.png|width=550,height=300!

          Maven launcher process:

          !maven-laucher.png|width=550,height=300!
          amuniz Antonio Muñiz made changes -
          Description 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.

          h3. Jenkins 1.x vs. 2.0 comparison running a single test ({{JDKInstallerTest}})

          h4. Jenkins 1.x

          1. Maven launcher process:

          !jenkins1-maven-launcher.png|width=400,height=300!

          2. Surefire booter:

          !jenkins1-surefire-booter.png|width=400,height=300!

          h4. Jenkins 2.0

          1. Maven launcher process

          !jenkins2-maven-launcher.png|width=400,height=300!

          2. Surefire booter

          !jenkins2-surefire-booter.png|width=400,height=300!

          h3. Running the full test suite (on 2.0, Maven 3.3.3 and Java 8):

          Surefire forked booter 1:

          !forked-booter-1.png|width=550,height=300!

          Surefire forked booter 2:

          !forked-booter-2.png|width=550,height=300!

          Maven launcher process:

          !maven-laucher.png|width=550,height=300!
          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.

          h3. Jenkins 1.x vs. 2.0 comparison running a single test ({{JDKInstallerTest}})

          h4. Jenkins 1.x

          1. Maven launcher process:

          !jenkins1-maven-launcher.png|width=400,height=300!

          2. Surefire booter:

          !jenkins1-surefire-booter.png|width=400,height=300!

          h4. Jenkins 2.0

          1. Maven launcher process

          !jenkins2-maven-launcher.png|width=400,height=300!

          2. Surefire booter

          !jenkins2-surefire-booter.png|width=400,height=300!

          h3. Running the full test suite (on 2.0, Maven 3.3.3 and Java 8):

          Surefire forked booter 1:

          !forked-booter-1.png|width=550,height=300!

          Surefire forked booter 2 (there is a little jconsole disconnection of ~4 minutes in my local env, but nothing remarkable happened in the middle):

          !forked-booter-2.png|width=550,height=300!

          Maven launcher process:

          !maven-laucher.png|width=550,height=300!
          amuniz Antonio Muñiz made changes -
          Attachment java7-forked-booter-1.png [ 32316 ]
          Attachment java7-forked-booter-2.png [ 32317 ]
          Attachment java7-maven-launcher.png [ 32318 ]
          amuniz Antonio Muñiz made changes -
          Description 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.

          h3. Jenkins 1.x vs. 2.0 comparison running a single test ({{JDKInstallerTest}})

          h4. Jenkins 1.x

          1. Maven launcher process:

          !jenkins1-maven-launcher.png|width=400,height=300!

          2. Surefire booter:

          !jenkins1-surefire-booter.png|width=400,height=300!

          h4. Jenkins 2.0

          1. Maven launcher process

          !jenkins2-maven-launcher.png|width=400,height=300!

          2. Surefire booter

          !jenkins2-surefire-booter.png|width=400,height=300!

          h3. Running the full test suite (on 2.0, Maven 3.3.3 and Java 8):

          Surefire forked booter 1:

          !forked-booter-1.png|width=550,height=300!

          Surefire forked booter 2 (there is a little jconsole disconnection of ~4 minutes in my local env, but nothing remarkable happened in the middle):

          !forked-booter-2.png|width=550,height=300!

          Maven launcher process:

          !maven-laucher.png|width=550,height=300!
          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.

          h3. Jenkins 1.x vs. 2.0 comparison running a single test ({{JDKInstallerTest}})

          h4. Jenkins 1.x

          1. Maven launcher process:

          !jenkins1-maven-launcher.png|width=400,height=300!

          2. Surefire booter:

          !jenkins1-surefire-booter.png|width=400,height=300!

          h4. Jenkins 2.0

          1. Maven launcher process

          !jenkins2-maven-launcher.png|width=400,height=300!

          2. Surefire booter

          !jenkins2-surefire-booter.png|width=400,height=300!

          h3. Running the full test suite (on 2.0, Maven 3.3.3 and Java 8):

          Surefire forked booter 1:

          !forked-booter-1.png|width=550,height=300!

          Surefire forked booter 2 (there is a little jconsole disconnection of ~4 minutes in my local env, but nothing remarkable happened in the middle):

          !forked-booter-2.png|width=550,height=300!

          Maven launcher process:

          !maven-laucher.png|width=550,height=300!

          h3. Running the full test suite (on 2.0, Maven 3.3.3 and Java 7):

          Surefire forked booter 1:

          !java7-forked-booter-1.png|width=750,height=250!

          Surefire forked booter 2:

          !java7-forked-booter-2.png|width=750,height=250!

          Maven launcher process:

          !java7-maven-launcher.png|width=750,height=250!
          amuniz Antonio Muñiz made changes -
          Attachment java7-1.x-surefire-booter1.png [ 32324 ]
          Attachment java7-1.x-surefire-booter2.png [ 32325 ]
          Attachment java7-1.x-maven-launcher.png [ 32326 ]
          amuniz Antonio Muñiz made changes -
          Description 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.

          h3. Jenkins 1.x vs. 2.0 comparison running a single test ({{JDKInstallerTest}})

          h4. Jenkins 1.x

          1. Maven launcher process:

          !jenkins1-maven-launcher.png|width=400,height=300!

          2. Surefire booter:

          !jenkins1-surefire-booter.png|width=400,height=300!

          h4. Jenkins 2.0

          1. Maven launcher process

          !jenkins2-maven-launcher.png|width=400,height=300!

          2. Surefire booter

          !jenkins2-surefire-booter.png|width=400,height=300!

          h3. Running the full test suite (on 2.0, Maven 3.3.3 and Java 8):

          Surefire forked booter 1:

          !forked-booter-1.png|width=550,height=300!

          Surefire forked booter 2 (there is a little jconsole disconnection of ~4 minutes in my local env, but nothing remarkable happened in the middle):

          !forked-booter-2.png|width=550,height=300!

          Maven launcher process:

          !maven-laucher.png|width=550,height=300!

          h3. Running the full test suite (on 2.0, Maven 3.3.3 and Java 7):

          Surefire forked booter 1:

          !java7-forked-booter-1.png|width=750,height=250!

          Surefire forked booter 2:

          !java7-forked-booter-2.png|width=750,height=250!

          Maven launcher process:

          !java7-maven-launcher.png|width=750,height=250!
          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.

          h3. Jenkins 1.x vs. 2.0 comparison running a single test ({{JDKInstallerTest}})

          h4. Jenkins 1.x

          1. Maven launcher process:

          !jenkins1-maven-launcher.png|width=400,height=300!

          2. Surefire booter:

          !jenkins1-surefire-booter.png|width=400,height=300!

          h4. Jenkins 2.0

          1. Maven launcher process

          !jenkins2-maven-launcher.png|width=400,height=300!

          2. Surefire booter

          !jenkins2-surefire-booter.png|width=400,height=300!

          h3. Running the full test suite (on 2.0, Maven 3.3.3 and Java 8):

          Surefire forked booter 1:

          !forked-booter-1.png|width=550,height=300!

          Surefire forked booter 2 (there is a little jconsole disconnection of ~4 minutes in my local env, but nothing remarkable happened in the middle):

          !forked-booter-2.png|width=550,height=300!

          Maven launcher process:

          !maven-laucher.png|width=550,height=300!

          h3. Running the full test suite (on 2.0, Maven 3.3.3 and Java 7):

          Surefire forked booter 1:

          !java7-forked-booter-1.png|width=750,height=250!

          Surefire forked booter 2:

          !java7-forked-booter-2.png|width=750,height=250!

          Maven launcher process:

          !java7-maven-launcher.png|width=750,height=250!

          h3. Running the full test suite (on 1.x, Maven 3.3.3 and Java 7):

          Surefire forked booter 1:

          !java7-1.x-surefire-booter1.png|width=750,height=200!

          Surefire forked booter 2:

          !java7-1.x-surefire-booter2.png|width=750,height=200!

          Maven launcher process:

          !java7-1.x-maven-launcher.png|width=750,height=200!
          amuniz Antonio Muñiz made changes -
          Description 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.

          h3. Jenkins 1.x vs. 2.0 comparison running a single test ({{JDKInstallerTest}})

          h4. Jenkins 1.x

          1. Maven launcher process:

          !jenkins1-maven-launcher.png|width=400,height=300!

          2. Surefire booter:

          !jenkins1-surefire-booter.png|width=400,height=300!

          h4. Jenkins 2.0

          1. Maven launcher process

          !jenkins2-maven-launcher.png|width=400,height=300!

          2. Surefire booter

          !jenkins2-surefire-booter.png|width=400,height=300!

          h3. Running the full test suite (on 2.0, Maven 3.3.3 and Java 8):

          Surefire forked booter 1:

          !forked-booter-1.png|width=550,height=300!

          Surefire forked booter 2 (there is a little jconsole disconnection of ~4 minutes in my local env, but nothing remarkable happened in the middle):

          !forked-booter-2.png|width=550,height=300!

          Maven launcher process:

          !maven-laucher.png|width=550,height=300!

          h3. Running the full test suite (on 2.0, Maven 3.3.3 and Java 7):

          Surefire forked booter 1:

          !java7-forked-booter-1.png|width=750,height=250!

          Surefire forked booter 2:

          !java7-forked-booter-2.png|width=750,height=250!

          Maven launcher process:

          !java7-maven-launcher.png|width=750,height=250!

          h3. Running the full test suite (on 1.x, Maven 3.3.3 and Java 7):

          Surefire forked booter 1:

          !java7-1.x-surefire-booter1.png|width=750,height=200!

          Surefire forked booter 2:

          !java7-1.x-surefire-booter2.png|width=750,height=200!

          Maven launcher process:

          !java7-1.x-maven-launcher.png|width=750,height=200!
          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.

          h2. Jenkins 1.x vs. 2.0 comparison running a single test ({{JDKInstallerTest}})

          h3. Jenkins 1.x

          1. Maven launcher process:

          !jenkins1-maven-launcher.png|width=400,height=300!

          2. Surefire booter:

          !jenkins1-surefire-booter.png|width=400,height=300!

          h3. Jenkins 2.0

          1. Maven launcher process

          !jenkins2-maven-launcher.png|width=400,height=300!

          2. Surefire booter

          !jenkins2-surefire-booter.png|width=400,height=300!

          h2. Running the full test suite (on 2.0, Maven 3.3.3 and Java 8):

          Surefire forked booter 1:

          !forked-booter-1.png|width=550,height=300!

          Surefire forked booter 2 (there is a little jconsole disconnection of ~4 minutes in my local env, but nothing remarkable happened in the middle):

          !forked-booter-2.png|width=550,height=300!

          Maven launcher process:

          !maven-laucher.png|width=550,height=300!

          h3. Running the full test suite (on 2.0, Maven 3.3.3 and Java 7):

          Surefire forked booter 1:

          !java7-forked-booter-1.png|width=750,height=250!

          Surefire forked booter 2:

          !java7-forked-booter-2.png|width=750,height=250!

          Maven launcher process:

          !java7-maven-launcher.png|width=750,height=250!

          h2. Running the full test suite (on 1.x, Maven 3.3.3 and Java 7):

          Surefire forked booter 1:

          !java7-1.x-surefire-booter1.png|width=750,height=200!

          Surefire forked booter 2:

          !java7-1.x-surefire-booter2.png|width=750,height=200!

          Maven launcher process:

          !java7-1.x-maven-launcher.png|width=750,height=200!
          amuniz Antonio Muñiz made changes -
          Description 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.

          h2. Jenkins 1.x vs. 2.0 comparison running a single test ({{JDKInstallerTest}})

          h3. Jenkins 1.x

          1. Maven launcher process:

          !jenkins1-maven-launcher.png|width=400,height=300!

          2. Surefire booter:

          !jenkins1-surefire-booter.png|width=400,height=300!

          h3. Jenkins 2.0

          1. Maven launcher process

          !jenkins2-maven-launcher.png|width=400,height=300!

          2. Surefire booter

          !jenkins2-surefire-booter.png|width=400,height=300!

          h2. Running the full test suite (on 2.0, Maven 3.3.3 and Java 8):

          Surefire forked booter 1:

          !forked-booter-1.png|width=550,height=300!

          Surefire forked booter 2 (there is a little jconsole disconnection of ~4 minutes in my local env, but nothing remarkable happened in the middle):

          !forked-booter-2.png|width=550,height=300!

          Maven launcher process:

          !maven-laucher.png|width=550,height=300!

          h3. Running the full test suite (on 2.0, Maven 3.3.3 and Java 7):

          Surefire forked booter 1:

          !java7-forked-booter-1.png|width=750,height=250!

          Surefire forked booter 2:

          !java7-forked-booter-2.png|width=750,height=250!

          Maven launcher process:

          !java7-maven-launcher.png|width=750,height=250!

          h2. Running the full test suite (on 1.x, Maven 3.3.3 and Java 7):

          Surefire forked booter 1:

          !java7-1.x-surefire-booter1.png|width=750,height=200!

          Surefire forked booter 2:

          !java7-1.x-surefire-booter2.png|width=750,height=200!

          Maven launcher process:

          !java7-1.x-maven-launcher.png|width=750,height=200!
          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.

          h2. Jenkins 1.x vs. 2.0 comparison running a single test ({{JDKInstallerTest}})

          h3. Jenkins 1.x

          1. Maven launcher process:

          !jenkins1-maven-launcher.png|width=400,height=300!

          2. Surefire booter:

          !jenkins1-surefire-booter.png|width=400,height=300!

          h3. Jenkins 2.0

          1. Maven launcher process

          !jenkins2-maven-launcher.png|width=400,height=300!

          2. Surefire booter

          !jenkins2-surefire-booter.png|width=400,height=300!

          h2. Running the full test suite (on 2.0, Maven 3.3.3 and Java 8):

          Surefire forked booter 1:

          !forked-booter-1.png|width=550,height=300!

          Surefire forked booter 2 (there is a little jconsole disconnection of ~4 minutes in my local env, but nothing remarkable happened in the middle):

          !forked-booter-2.png|width=550,height=300!

          Maven launcher process:

          !maven-laucher.png|width=550,height=300!

          h2. Running the full test suite (on 2.0, Maven 3.3.3 and Java 7):

          Surefire forked booter 1:

          !java7-forked-booter-1.png|width=750,height=250!

          Surefire forked booter 2:

          !java7-forked-booter-2.png|width=750,height=250!

          Maven launcher process:

          !java7-maven-launcher.png|width=750,height=250!

          h2. Running the full test suite (on 1.x, Maven 3.3.3 and Java 7):

          Surefire forked booter 1:

          !java7-1.x-surefire-booter1.png|width=750,height=200!

          Surefire forked booter 2:

          !java7-1.x-surefire-booter2.png|width=750,height=200!

          Maven launcher process:

          !java7-1.x-maven-launcher.png|width=750,height=200!
          amuniz Antonio Muñiz made changes -
          Description 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.

          h2. Jenkins 1.x vs. 2.0 comparison running a single test ({{JDKInstallerTest}})

          h3. Jenkins 1.x

          1. Maven launcher process:

          !jenkins1-maven-launcher.png|width=400,height=300!

          2. Surefire booter:

          !jenkins1-surefire-booter.png|width=400,height=300!

          h3. Jenkins 2.0

          1. Maven launcher process

          !jenkins2-maven-launcher.png|width=400,height=300!

          2. Surefire booter

          !jenkins2-surefire-booter.png|width=400,height=300!

          h2. Running the full test suite (on 2.0, Maven 3.3.3 and Java 8):

          Surefire forked booter 1:

          !forked-booter-1.png|width=550,height=300!

          Surefire forked booter 2 (there is a little jconsole disconnection of ~4 minutes in my local env, but nothing remarkable happened in the middle):

          !forked-booter-2.png|width=550,height=300!

          Maven launcher process:

          !maven-laucher.png|width=550,height=300!

          h2. Running the full test suite (on 2.0, Maven 3.3.3 and Java 7):

          Surefire forked booter 1:

          !java7-forked-booter-1.png|width=750,height=250!

          Surefire forked booter 2:

          !java7-forked-booter-2.png|width=750,height=250!

          Maven launcher process:

          !java7-maven-launcher.png|width=750,height=250!

          h2. Running the full test suite (on 1.x, Maven 3.3.3 and Java 7):

          Surefire forked booter 1:

          !java7-1.x-surefire-booter1.png|width=750,height=200!

          Surefire forked booter 2:

          !java7-1.x-surefire-booter2.png|width=750,height=200!

          Maven launcher process:

          !java7-1.x-maven-launcher.png|width=750,height=200!
          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.

          h2. Running the full test suite (on 2.0, Maven 3.3.3 and Java 8):

          Surefire forked booter 1:

          !forked-booter-1.png|width=550,height=300!

          Surefire forked booter 2 (there is a little jconsole disconnection of ~4 minutes in my local env, but nothing remarkable happened in the middle):

          !forked-booter-2.png|width=550,height=300!

          Maven launcher process:

          !maven-laucher.png|width=550,height=300!

          h2. Running the full test suite (on 2.0, Maven 3.3.3 and Java 7):

          Surefire forked booter 1:

          !java7-forked-booter-1.png|width=750,height=250!

          Surefire forked booter 2:

          !java7-forked-booter-2.png|width=750,height=250!

          Maven launcher process:

          !java7-maven-launcher.png|width=750,height=250!

          h2. Running the full test suite (on 1.x, Maven 3.3.3 and Java 7):

          Surefire forked booter 1:

          !java7-1.x-surefire-booter1.png|width=750,height=200!

          Surefire forked booter 2:

          !java7-1.x-surefire-booter2.png|width=750,height=200!

          Maven launcher process:

          !java7-1.x-maven-launcher.png|width=750,height=200!
          amuniz Antonio Muñiz made changes -
          Attachment java7-forked-booter-1.png [ 32316 ]
          amuniz Antonio Muñiz made changes -
          Attachment java7-forked-booter-2.png [ 32317 ]
          amuniz Antonio Muñiz made changes -
          Attachment java7-maven-launcher.png [ 32318 ]
          amuniz Antonio Muñiz made changes -
          Attachment java7-2.0-surefire-booter1.png [ 32327 ]
          Attachment java7-2.0-surefire-booter2.png [ 32328 ]
          Attachment java7-2.0-maven-launcher.png [ 32329 ]
          amuniz Antonio Muñiz made changes -
          Description 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.

          h2. Running the full test suite (on 2.0, Maven 3.3.3 and Java 8):

          Surefire forked booter 1:

          !forked-booter-1.png|width=550,height=300!

          Surefire forked booter 2 (there is a little jconsole disconnection of ~4 minutes in my local env, but nothing remarkable happened in the middle):

          !forked-booter-2.png|width=550,height=300!

          Maven launcher process:

          !maven-laucher.png|width=550,height=300!

          h2. Running the full test suite (on 2.0, Maven 3.3.3 and Java 7):

          Surefire forked booter 1:

          !java7-forked-booter-1.png|width=750,height=250!

          Surefire forked booter 2:

          !java7-forked-booter-2.png|width=750,height=250!

          Maven launcher process:

          !java7-maven-launcher.png|width=750,height=250!

          h2. Running the full test suite (on 1.x, Maven 3.3.3 and Java 7):

          Surefire forked booter 1:

          !java7-1.x-surefire-booter1.png|width=750,height=200!

          Surefire forked booter 2:

          !java7-1.x-surefire-booter2.png|width=750,height=200!

          Maven launcher process:

          !java7-1.x-maven-launcher.png|width=750,height=200!
          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.

          h2. Running the full test suite (on 2.0, Maven 3.3.3 and Java 8):

          Surefire forked booter 1:

          !forked-booter-1.png|width=550,height=300!

          Surefire forked booter 2 (there is a little jconsole disconnection of ~4 minutes in my local env, but nothing remarkable happened in the middle):

          !forked-booter-2.png|width=550,height=300!

          Maven launcher process:

          !maven-laucher.png|width=550,height=300!

          h2. Running the full test suite (on 2.0, Maven 3.3.3 and Java 7):

          Surefire forked booter 1:

          !java7-2.0-surefire-booter1.png|width=750,height=200!

          Surefire forked booter 2:

          !java7-2.0-surefire-booter2.png|width=750,height=200!

          Maven launcher process:

          !java7-2.0-maven-launcher.png|width=750,height=200!

          h2. Running the full test suite (on 1.x, Maven 3.3.3 and Java 7):

          Surefire forked booter 1:

          !java7-1.x-surefire-booter1.png|width=750,height=200!

          Surefire forked booter 2:

          !java7-1.x-surefire-booter2.png|width=750,height=200!

          Maven launcher process:

          !java7-1.x-maven-launcher.png|width=750,height=200!
          amuniz Antonio Muñiz made changes -
          Description 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.

          h2. Running the full test suite (on 2.0, Maven 3.3.3 and Java 8):

          Surefire forked booter 1:

          !forked-booter-1.png|width=550,height=300!

          Surefire forked booter 2 (there is a little jconsole disconnection of ~4 minutes in my local env, but nothing remarkable happened in the middle):

          !forked-booter-2.png|width=550,height=300!

          Maven launcher process:

          !maven-laucher.png|width=550,height=300!

          h2. Running the full test suite (on 2.0, Maven 3.3.3 and Java 7):

          Surefire forked booter 1:

          !java7-2.0-surefire-booter1.png|width=750,height=200!

          Surefire forked booter 2:

          !java7-2.0-surefire-booter2.png|width=750,height=200!

          Maven launcher process:

          !java7-2.0-maven-launcher.png|width=750,height=200!

          h2. Running the full test suite (on 1.x, Maven 3.3.3 and Java 7):

          Surefire forked booter 1:

          !java7-1.x-surefire-booter1.png|width=750,height=200!

          Surefire forked booter 2:

          !java7-1.x-surefire-booter2.png|width=750,height=200!

          Maven launcher process:

          !java7-1.x-maven-launcher.png|width=750,height=200!
          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.

          h2. Running the full test suite (on 2.0, Maven 3.3.3 and Java 8):

          Surefire forked booter 1:

          !forked-booter-1.png|width=550,height=300!

          Surefire forked booter 2 (there is a little jconsole disconnection of ~4 minutes in my local env, but nothing remarkable happened in the middle):

          !forked-booter-2.png|width=550,height=300!

          Maven launcher process:

          !maven-laucher.png|width=550,height=300!

          h2. 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:

          !java7-2.0-surefire-booter1.png|width=750,height=200!

          Surefire forked booter 2:

          !java7-2.0-surefire-booter2.png|width=750,height=200!

          Maven launcher process:

          !java7-2.0-maven-launcher.png|width=750,height=200!

          h2. Running the full test suite (on 1.x, Maven 3.3.3 and Java 7 and -Xmx256):

          Surefire forked booter 1:

          !java7-1.x-surefire-booter1.png|width=750,height=200!

          Surefire forked booter 2:

          !java7-1.x-surefire-booter2.png|width=750,height=200!

          Maven launcher process:

          !java7-1.x-maven-launcher.png|width=750,height=200!
          danielbeck Daniel Beck made changes -
          Resolution Done [ 10000 ]
          Status In Progress [ 3 ] Resolved [ 5 ]
          rtyler R. Tyler Croy made changes -
          Workflow JNJira [ 169803 ] JNJira + In-Review [ 198694 ]

            People

            Assignee:
            amuniz Antonio Muñiz
            Reporter:
            danielbeck Daniel Beck
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: