• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • core
    • Jenkins 2.150
      Windows 7
      cygwin

      After executing successfully the shell script the workers remain stuck for 10 minutes on the final "exit 0".

      There hasn't been any other failure that I could find: all the jobs run exactly as planned, they just don't seem to exit.

      The fact that the jobs remain stuck for exactly 600 seconds makes me think of a timeout of some sort.

      Reverting to 2.138 fixed the issue, that's why I am marking it as a regression.

          [JENKINS-55106] Build stuck on final "exit 0"

          Michele Ippolito created issue -

          Guru Vamsi Chintala added a comment - - edited

          We are seeing the same issue in regular builds and pull requests, build stucks on exit 0 for more than 5 minutes and reports the status.

          Guru Vamsi Chintala added a comment - - edited We are seeing the same issue in regular builds and pull requests, build stucks on exit 0 for more than 5 minutes and reports the status.

          Sean Kline added a comment -

          We are seeing this issue as well on version 2.150.1 running on Windows Server 2012 R2. Builds that took 4 minutes prior to the upgrade were taking 18 minutes afterward. We have reverted to version 2.138.3, which resolved the issue.

          If there's information that I can provide to help pin this down, please let me know.

          Sean Kline added a comment - We are seeing this issue as well on version 2.150.1 running on Windows Server 2012 R2. Builds that took 4 minutes prior to the upgrade were taking 18 minutes afterward. We have reverted to version 2.138.3, which resolved the issue. If there's information that I can provide to help pin this down, please let me know.

          Reverting the jenkins version to 2.138.3 fixed the issue. Hope it is fixed in next Jenkins LTS version.

          Thank you  Sean.

          Guru Vamsi Chintala added a comment - Reverting the jenkins version to 2.138.3 fixed the issue. Hope it is fixed in next Jenkins LTS version. Thank you  Sean.

          Anatoly Shirokov added a comment - - edited

          Confirmed. The same issue with 2.150.1 on Windows Server 2003, JDK 8. As you see exactly 10 minutes before the finish:

           

           19:59:42 D:\Jenkins\jobs\product\workspace>echo done 
           19:59:42 done
           19:59:42 
           19:59:42 D:\Jenkins\jobs\product\workspace>exit 0 
           20:09:44 Finished: SUCCESS
          

          We have reverted to the 2.138.2 version.

           

           

          Anatoly Shirokov added a comment - - edited Confirmed. The same issue with 2.150.1 on Windows Server 2003, JDK 8. As you see exactly 10 minutes before the finish:   19:59:42 D:\Jenkins\jobs\product\workspace>echo done 19:59:42 done 19:59:42 19:59:42 D:\Jenkins\jobs\product\workspace>exit 0 20:09:44 Finished: SUCCESS We have reverted to the 2.138.2 version.    
          Anatoly Shirokov made changes -
          Priority Original: Minor [ 4 ] New: Critical [ 2 ]

          Shawn Baker added a comment -

          I can also confirmed this on Windows Server 2012 R2, JDK 8 on Jenkins 2.150.2.  After the Build portion of the configuration has completed, there is a 10 minute delay before the Post-build Actions begin.

          I reverted back to 2.138.4.

          Shawn Baker added a comment - I can also confirmed this on Windows Server 2012 R2, JDK 8 on Jenkins 2.150.2.  After the Build portion of the configuration has completed, there is a 10 minute delay before the Post-build Actions begin. I reverted back to 2.138.4.

          I tried upgrading my instance to 2.164 and I can still reproduce it. I'll revert again to 2.138 for the moment.

          I'll lose access to this instance soon (~3 weeks) so if anyone needs me to try stuff, now's the time.

          Michele Ippolito added a comment - I tried upgrading my instance to 2.164 and I can still reproduce it. I'll revert again to 2.138 for the moment. I'll lose access to this instance soon (~3 weeks) so if anyone needs me to try stuff, now's the time.

          Added "-DSoftKillWaitSeconds=0 " in jenkins.xml before the -jar option. Now jobs execute normally with 2.150.2 version
          Reference: https://stackoverflow.com/questions/54039226/jenkins-hangs-between-build-and-post-build/54072987#54072987
                           https://issues.jenkins-ci.org/browse/JENKINS-55422?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel

          Guru Vamsi Chintala added a comment - Added "-DSoftKillWaitSeconds=0 " in jenkins.xml before the -jar option. Now jobs execute normally with 2.150.2 version Reference: https://stackoverflow.com/questions/54039226/jenkins-hangs-between-build-and-post-build/54072987#54072987                   https://issues.jenkins-ci.org/browse/JENKINS-55422?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel

          Sean Kline added a comment -

          Thank you very much for pointing this out, Guru. We tried this and are now running 2.150.2 without the delay.

          Have a great day!

          Sean Kline added a comment - Thank you very much for pointing this out, Guru. We tried this and are now running 2.150.2 without the delay. Have a great day!

            Unassigned Unassigned
            ippo343 Michele Ippolito
            Votes:
            22 Vote for this issue
            Watchers:
            31 Start watching this issue

              Created:
              Updated: