• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • xvfb-plugin
    • None

      When a connection to a slave is unexpectedly broken during a build, an Xvfb process started by the plugin is not killed. After the slave is reconnected, subsequent builds on it fail immediately because the plugin tries to start a new Xvfb process on the same display as the old one.

      It would be helpful if the plugin could kill left over Xvfb processes before trying to start a new one. There could be a configuration option to kill all Xvfb processes. More robustly, it could probably find just the problematic one by command line.

          [JENKINS-20758] Xvfb processes remain after slave disconnect

          Jonathan Rogers created issue -
          zregvart made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          zregvart made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 152567 ] New: JNJira + In-Review [ 207197 ]

            zregvart zregvart
            jrogers Jonathan Rogers
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: