ProcessTreeKiller broken for Windows when node went offline/online

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Critical
    • Component/s: core
    • Environment:
      Jenkins 1.625.1 LTS
      Window7,Window8,Window10 node
      JDK 1.7

      1) Choose a Windows7/8/10 node and mark it offline in its configuration page
      2) then mark it online
      3) Create a job attached to this node with the Windows command: notepad.exe
      4) Start your job, check that Notepad is started (dont close).
      5) Cancel the build of the job and see that Notepad is still open.

      On the windows node, if you manually restart the agent, this fixes the "kill behavior".

      the problem also happens for an accidental deconnection/reconnection (that how we notificed that, because randomly it seems that the ProcessTreeKiller did not work anymore and it seemed that it happened after networks issues between the server and the node)

            Assignee:
            Unassigned
            Reporter:
            Stephane Gallès
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: