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

Jacoco Memory Allocation after Job is Terminated

    Details

    • Similar Issues:

      Description

      In my multimodule project I am using Jacoco test coverage and Jacoco-plugin in Jenkins.

      I start some job in my Jenkins, when it comes to the test phase, Jacoco process will be created and after job execution the process will be closed. But when the job is stucked in the test phase, the only way is to terminate the job. But in this case the Jacoco process won't be closed, even after the Jenkins restart. The only way is to kill the process.

      I have one Jenkins running on my physical machine and another one in docker. Problem occures in both cases.

      Steps to reproduce:

      1. Start the job.
      2. Make it stuck in test phase.
      3. Terminate the job (X button in Build History window)
      4. Check the running processes(top/htop).
      5. (Optional)Restart jenkins.
      6. (Optional) Check the active processes. 

       

        Attachments

          Activity

          Hide
          centic centic added a comment -

          The jacoco-plugin does not start any process, it just collects results from a previous result, so I don't think the plugin is related here.

           

          Also please provide some log to let developers see how far the process is executed.

          Show
          centic centic added a comment - The jacoco-plugin does not start any process, it just collects results from a previous result, so I don't think the plugin is related here.   Also please provide some log to let developers see how far the process is executed.
          Hide
          tsologub Taras Sologub added a comment -

          I am not sure if it was Jacoco-plugin issue. I have built already a workaround for that.

          If somebody is interested : http://stackoverflow.com/questions/42786787/jacoco-memory-allocation-after-job-is-terminated

          Unfortunately there is nothing to track in the log file. If nobody has never seen the similar issues, I would suggest to close the ticket. 

           

          Show
          tsologub Taras Sologub added a comment - I am not sure if it was Jacoco-plugin issue. I have built already a workaround for that. If somebody is interested : http://stackoverflow.com/questions/42786787/jacoco-memory-allocation-after-job-is-terminated Unfortunately there is nothing to track in the log file. If nobody has never seen the similar issues, I would suggest to close the ticket.   
          Hide
          centic centic added a comment -

          This seems to be more related to JaCoCo itself, not Jenkins, there closing this here.

          Show
          centic centic added a comment - This seems to be more related to JaCoCo itself, not Jenkins, there closing this here.

            People

            • Assignee:
              ognjenb Ognjen Bubalo
              Reporter:
              tsologub Taras Sologub
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: