• Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Minor Minor
    • core
    • None
    • Docker/Ubuntu LTS 2.89.4

      After upgrading to LTS 2.89.4 the estimate time remaining is always NA

          [JENKINS-49616] Estimated time remaining NA

          uncletall created issue -

          Oleg Nenashev added a comment -

          Please provide more info about the issue: Job types you use, UI screenshots, etc.

          Oleg Nenashev added a comment - Please provide more info about the issue: Job types you use, UI screenshots, etc.
          uncletall made changes -

          uncletall added a comment -

          The jobs are different kind of pipeline jobs.

          uncletall added a comment - The jobs are different kind of pipeline jobs.
          Benjamin Coover made changes -
          Attachment New: pipeline_remaining01.png [ 41544 ]
          Attachment New: pipeline_remaining02.png [ 41545 ]

          We are seeing this as well. Our jobs are regular pipelines (Scripted-style, as opposed to Declarative) using Jenkinsfile from SCM. The nodes being used are Windows 7 and Ubuntu 14.04 virtual machines and master is Windows Server 2012. Freestyle jobs still display estimated remaining time.

          Benjamin Coover added a comment - We are seeing this as well. Our jobs are regular pipelines (Scripted-style, as opposed to Declarative) using Jenkinsfile from SCM. The nodes being used are Windows 7 and Ubuntu 14.04 virtual machines and master is Windows Server 2012. Freestyle jobs still display estimated remaining time.
          Matthias Keller made changes -
          Attachment New: image-2018-02-21-19-28-24-208.png [ 41559 ]

          Matthias Keller added a comment - - edited

          Same here, we're seeing this since the last updates. Most projects are pipelines as well. Right after starting (and probably before the pipeline really starts), the ETA is displayed. However, shortly afterwards and until the build is completely finished, the time isn't here anymore:

          According to https://groups.google.com/forum/#!topic/jenkinsci-users/BdKmRrkjir4 the bug is very easy to fix:

          Resetting the executableEstimatedDuration only when there is no asynchrounous execution seems to solve the problem. So the resulting Code in hudson.model.Executor is

          [...]
          458 } finally {
          459  if (asynchronousExecution == null) {
          460   finish2();
          461   executableEstimatedDuration = DEFAULT_ESTIMATED_DURATION;
          462  }
          463 }
          [...]

          Matthias Keller added a comment - - edited Same here, we're seeing this since the last updates. Most projects are pipelines as well. Right after starting (and probably before the pipeline really starts), the ETA is displayed. However, shortly afterwards and until the build is completely finished, the time isn't here anymore: According to https://groups.google.com/forum/#!topic/jenkinsci-users/BdKmRrkjir4 the bug is very easy to fix: Resetting the executableEstimatedDuration only when there is no asynchrounous execution seems to solve the problem. So the resulting Code in hudson.model.Executor is [...] 458 } finally { 459 if (asynchronousExecution == null ) { 460 finish2(); 461 executableEstimatedDuration = DEFAULT_ESTIMATED_DURATION; 462 } 463 } [...]

          Aaron Curley added a comment -

          Also seeing this on LTS 2.89.4 after upgrading from 2.89.2.

          Aaron Curley added a comment - Also seeing this on LTS 2.89.4 after upgrading from 2.89.2.

          Henti Smith added a comment -

          Same problem after upgrading to LTS on all our builds. 

          Henti Smith added a comment - Same problem after upgrading to LTS on all our builds. 

            Unassigned Unassigned
            uncletall uncletall
            Votes:
            6 Vote for this issue
            Watchers:
            13 Start watching this issue

              Created:
              Updated:
              Resolved: