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

    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

          Hide
          amuniz Antonio Muñiz added a comment -

          Daniel Beck Ok, so my theory is... wrong

          Show
          amuniz Antonio Muñiz added a comment - Daniel Beck Ok, so my theory is... wrong
          Hide
          danielbeck Daniel Beck added a comment -

          Antonio Muñiz Do we need to reopen this?

          Show
          danielbeck Daniel Beck added a comment - Antonio Muñiz Do we need to reopen this?
          Hide
          amuniz Antonio Muñiz added a comment -

          Daniel Beck I don't think so. I could not reproduce the OOM locally (after many full runs). The issues we saw yesterday in https://ci.jenkins-ci.org did not reproduce after cleaning all zombie processes in celery node.

          So not much more to do, just merge https://github.com/jenkinsci/jenkins/pull/2220 and wait for the OOM to happen again (or perhaps it does not happen anymore).

          Show
          amuniz Antonio Muñiz added a comment - Daniel Beck I don't think so. I could not reproduce the OOM locally (after many full runs). The issues we saw yesterday in https://ci.jenkins-ci.org did not reproduce after cleaning all zombie processes in celery node. So not much more to do, just merge https://github.com/jenkinsci/jenkins/pull/2220 and wait for the OOM to happen again (or perhaps it does not happen anymore).
          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Daniel Beck
          Path:
          test/pom.xml
          http://jenkins-ci.org/commit/jenkins/0d0314ddee72b227a770d294549d12ded3b3fbac
          Log:
          JENKINS-33809 Don't reuse forks

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Daniel Beck Path: test/pom.xml http://jenkins-ci.org/commit/jenkins/0d0314ddee72b227a770d294549d12ded3b3fbac Log: JENKINS-33809 Don't reuse forks
          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Daniel Beck
          Path:
          test/pom.xml
          http://jenkins-ci.org/commit/jenkins/574f83a962a62021cc60b6af1e3de5c0f1f008b8
          Log:
          Merge pull request #2264 from daniel-beck/reuseForks=false

          JENKINS-33809 Don't reuse forks

          Compare: https://github.com/jenkinsci/jenkins/compare/4f51944cf1f9...574f83a962a6

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Daniel Beck Path: test/pom.xml http://jenkins-ci.org/commit/jenkins/574f83a962a62021cc60b6af1e3de5c0f1f008b8 Log: Merge pull request #2264 from daniel-beck/reuseForks=false JENKINS-33809 Don't reuse forks Compare: https://github.com/jenkinsci/jenkins/compare/4f51944cf1f9...574f83a962a6

            People

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

              Dates

              • Created:
                Updated:
                Resolved: