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

Jobs remain on executor for 20 minutes after they finish

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • core
    • None
    • Jenkins 1.447

      I recently upgraded Jenkins to 1.447 and enabled the hudson.upstreamCulprits setting. When my Maven2/3 job runs, it completes normally from the console perspective, but on the main build page, the executors show that it is still running. I used the monitoring plugin to inspect the threads and found that it seems to be trying to figure out which logs to keep. This process seems to run for about 20 minutes. I am guessing this may have something to do with the number of builds. Here's a sample stack trace of the executor:

      Executor #0 for master : executing aat-tao-3.8 #805
      java.util.ArrayList.size(ArrayList.java:177)
      java.util.AbstractList$Itr.hasNext(AbstractList.java:339)
      hudson.maven.MavenModuleSetBuild.getDownstreamRelationship(MavenModuleSetBuild.java:489)
      hudson.model.AbstractBuild.getWhyKeepLog(AbstractBuild.java:986)
      hudson.maven.MavenBuild.getWhyKeepLog(MavenBuild.java:264)
      hudson.model.Run.isKeepLog(Run.java:470)
      hudson.tasks.LogRotator.perform(LogRotator.java:140)
      hudson.model.Job.logRotate(Job.java:326)
      hudson.maven.MavenModuleSet.logRotate(MavenModuleSet.java:712)
      hudson.model.Run.run(Run.java:1469)
      hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:481)
      hudson.model.ResourceController.execute(ResourceController.java:88)
      hudson.model.Executor.run(Executor.java:238)

            Unassigned Unassigned
            petehayes Peter Hayes
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: