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

Job status page shows "Build has been executing for null on master"

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • core
    • None
    • Jenkins v 1.357
      Windows 7
      Windows service

      I was watching the build page, and saw that the following text to the upper right "Build has been executing for null on master"

      I was not expected "null" in the message

          [JENKINS-20307] Job status page shows "Build has been executing for null on master"

          Michael Rose added a comment -

          I am seeing this issue on version 1.559 for my multi-configuration (matrix) project.

          Started 6 min 42 sec ago
          Build has been executing for null on

          Michael Rose added a comment - I am seeing this issue on version 1.559 for my multi-configuration (matrix) project. Started 6 min 42 sec ago Build has been executing for null on

          Daniel Beck added a comment -

          Michael:

          Which of the Matrix builds shows this message? The parent? A regular configuration's build?
          Is there no node name specified (i.e. 'Build has been executing for null on' rather than 'Build has been executing for null on master' as described above)?

          Daniel Beck added a comment - Michael: Which of the Matrix builds shows this message? The parent? A regular configuration's build? Is there no node name specified (i.e. 'Build has been executing for null on' rather than 'Build has been executing for null on master' as described above)?

          Michael Rose added a comment -

          It is the parent. The configuration build seem to have the correct description.

          Sorry I accidentally clipped off the host last time. The on "HOSTNAME" portion of the string is correct.

          Started 46 sec ago
          Build has been executing for null on b261806

          Michael Rose added a comment - It is the parent. The configuration build seem to have the correct description. Sorry I accidentally clipped off the host last time. The on "HOSTNAME" portion of the string is correct. Started 46 sec ago Build has been executing for null on b261806

          Daniel Beck added a comment -

          I'm almost sure I found the cause in Run.getExecutor().

          Workaround should be -Dhudson.model.Hudson.flyweightSupport=false, because it affects only Flyweight tasks that run on One-off executors.

          Daniel Beck added a comment - I'm almost sure I found the cause in Run.getExecutor() . Workaround should be -Dhudson.model.Hudson.flyweightSupport=false , because it affects only Flyweight tasks that run on One-off executors.

          jlongman added a comment -

          Also seeing this on 1.571 hosted on a FreeBSD 9.1 machine.

          Started 3 hr 21 min ago
          Build has been executing for null on xlicenses

          May be related to null time refereces in the build progress column plugin, which shows

          Started null ago
          Estimated time remaining null

          (May because the actual parent job has a non-null time for Started ago.)

          jlongman added a comment - Also seeing this on 1.571 hosted on a FreeBSD 9.1 machine. Started 3 hr 21 min ago Build has been executing for null on xlicenses May be related to null time refereces in the build progress column plugin, which shows Started null ago Estimated time remaining null (May because the actual parent job has a non-null time for Started ago.)

          Daniel Beck added a comment -

          See above linked PR 1348 for an explanation and proposed solution.

          Daniel Beck added a comment - See above linked PR 1348 for an explanation and proposed solution.

          Code changed in jenkins
          User: Daniel Beck
          Path:
          core/src/main/java/hudson/model/Run.java
          http://jenkins-ci.org/commit/jenkins/9379d1fefc49fbe8cf11bb96290a9924a6eb38cc
          Log:
          [FIXED JENKINS-20307] Consider OneOffExecutors in Run.getExecutor()

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/model/Run.java http://jenkins-ci.org/commit/jenkins/9379d1fefc49fbe8cf11bb96290a9924a6eb38cc Log: [FIXED JENKINS-20307] Consider OneOffExecutors in Run.getExecutor()

          Code changed in jenkins
          User: Daniel Beck
          Path:
          core/src/main/java/hudson/model/Run.java
          http://jenkins-ci.org/commit/jenkins/fe3b33a16e850f1e5a5fd80b06b3484eb6f4bf98
          Log:
          Merge pull request #1348 from daniel-beck/JENKINS-20307

          [FIXED JENKINS-20307] Consider OneOffExecutors in Run.getExecutor()

          Compare: https://github.com/jenkinsci/jenkins/compare/174786b9f758...fe3b33a16e85

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/model/Run.java http://jenkins-ci.org/commit/jenkins/fe3b33a16e850f1e5a5fd80b06b3484eb6f4bf98 Log: Merge pull request #1348 from daniel-beck/ JENKINS-20307 [FIXED JENKINS-20307] Consider OneOffExecutors in Run.getExecutor() Compare: https://github.com/jenkinsci/jenkins/compare/174786b9f758...fe3b33a16e85

          dogfood added a comment -

          Integrated in jenkins_main_trunk #3651
          [FIXED JENKINS-20307] Consider OneOffExecutors in Run.getExecutor() (Revision 9379d1fefc49fbe8cf11bb96290a9924a6eb38cc)

          Result = SUCCESS
          daniel-beck : 9379d1fefc49fbe8cf11bb96290a9924a6eb38cc
          Files :

          • core/src/main/java/hudson/model/Run.java

          dogfood added a comment - Integrated in jenkins_main_trunk #3651 [FIXED JENKINS-20307] Consider OneOffExecutors in Run.getExecutor() (Revision 9379d1fefc49fbe8cf11bb96290a9924a6eb38cc) Result = SUCCESS daniel-beck : 9379d1fefc49fbe8cf11bb96290a9924a6eb38cc Files : core/src/main/java/hudson/model/Run.java

          Pranav Gupta added a comment -

          I ran the following script to run the jenkins jobs

          import hudson.console.HyperlinkNote
          import java.util.concurrent.CancellationException
          import com.tikal.jenkins.plugins.multijob.MultiJobProject
          import hudson.model.*
          import hudson.AbortException

          job = hudson.model.Hudson.instance.items.each { job ->
          try {
          def running = job.lastBuild.building
          def disabled = job.isDisabled()
          def numbuilds = job.builds.size()
          lastbuild = job.builds[0]
          if (numbuilds == 0)

          { println job.name + ' has 0 previous build' }

          else if (running) {
          println "${job.name} is already running. Not launching"
          } else if (disabled) {
          println "${job.name} is disabled...Cannot be kicked off"
          } else {
          def buildParameter = job.builds[0].getAction(ParametersAction.class)
          if (buildParameter == null)

          { job.newBuild() println job.name + ' starts running...' }

          }
          } catch(Exception e)

          { println job.name + ' -> ' + e.getMessage() }

          }

          The jobs shows blinking green button but they are not running.
          Message : Build has been executing for null on master

          Pranav Gupta added a comment - I ran the following script to run the jenkins jobs import hudson.console.HyperlinkNote import java.util.concurrent.CancellationException import com.tikal.jenkins.plugins.multijob.MultiJobProject import hudson.model.* import hudson.AbortException job = hudson.model.Hudson.instance.items.each { job -> try { def running = job.lastBuild.building def disabled = job.isDisabled() def numbuilds = job.builds.size() lastbuild = job.builds [0] if (numbuilds == 0) { println job.name + ' has 0 previous build' } else if (running) { println "${job.name} is already running. Not launching" } else if (disabled) { println "${job.name} is disabled...Cannot be kicked off" } else { def buildParameter = job.builds [0] .getAction(ParametersAction.class) if (buildParameter == null) { job.newBuild() println job.name + ' starts running...' } } } catch(Exception e) { println job.name + ' -> ' + e.getMessage() } } The jobs shows blinking green button but they are not running. Message : Build has been executing for null on master

            danielbeck Daniel Beck
            redsolo redsolo
            Votes:
            2 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: