Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Critical
    • Resolution: Unresolved
    • Component/s: core
    • Labels:
    • Environment:
      Jenkins 2.150
      Windows 7
      cygwin
    • Similar Issues:

      Description

      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.

        Attachments

          Issue Links

            Activity

            Hide
            danielbeck Daniel Beck added a comment -

            Right, Josh wrote that. Would still like explicit confirmation from someone affected that setting it doesn't work, including confirmation that it appears correctly on the URL /computer/name_here/systemInfo in the list of system properties, since it's easy to get the Java invocation wrong.

            Show
            danielbeck Daniel Beck added a comment - Right, Josh wrote that. Would still like explicit confirmation from someone affected that setting it doesn't work, including confirmation that it appears correctly on the URL /computer/name_here/systemInfo in the list of system properties, since it's easy to get the Java invocation wrong.
            Hide
            joshschreuder Josh Schreuder added a comment -

            Daniel Beck

            Here's the slave command line:

            And from jenkins-slave.xml

            I'm pretty confident that this invocation is correct, as it's copied from our master agent where this parameter is working fine.

            Show
            joshschreuder Josh Schreuder added a comment - Daniel Beck Here's the slave command line: And from jenkins-slave.xml I'm pretty confident that this invocation is correct, as it's copied from our master agent where this parameter is working fine.
            Hide
            scb147 Shawn Baker added a comment - - edited

            Any progress with this? I understand that there is a workaround, but shouldn't the commit that broke it be looked at to at least see why it's broken?

            Show
            scb147 Shawn Baker added a comment - - edited Any progress with this? I understand that there is a workaround, but shouldn't the commit that broke it be looked at to at least see why it's broken?
            Hide
            pmascha Philipp Mascha added a comment -

            Can you please fix this? 

            Show
            pmascha Philipp Mascha added a comment - Can you please fix this? 
            Hide
            fsteff Flemming Steffensen added a comment -

            We've had this problem for 6 months or more, and have been searching high and low for a solution, without finding this issue.

            Just applied the workaround on one of our agents, and immediately cut down the build-time of one of our jobs by 25 minutes!!!!!!!!!! 

            I can't wait to see how much server time will be freed by this, but it looks like a LOT!

            Show
            fsteff Flemming Steffensen added a comment - We've had this problem for 6 months or more, and have been searching high and low for a solution, without finding this issue. Just applied the workaround on one of our agents, and immediately cut down the build-time of one of our jobs by 25 minutes!!!!!!!!!!  I can't wait to see how much server time will be freed by this, but it looks like a LOT!

              People

              • Assignee:
                Unassigned
                Reporter:
                ippo343 Michele Ippolito
              • Votes:
                19 Vote for this issue
                Watchers:
                29 Start watching this issue

                Dates

                • Created:
                  Updated: