[JIRA] [sauce-ondemand-plugin] (JENKINS-26288) Sauce connect remains running when test job is cancelled
Ross Rowe resolved JENKINS-26288 as Fixed Sauce connect remains running when test job is cancelled I've released version 1.114 of the plugin which should resolve this issue - it now includes some checks to see if there is a mismatch between the process count and the active tunnels. Please let me know if you still experience the behavior. Change By: Ross Rowe (27/Jan/15 9:11 AM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand-plugin] (JENKINS-26288) Sauce connect remains running when test job is cancelled
Ross Rowe started work on JENKINS-26288 Sauce connect remains running when test job is cancelled Change By: Ross Rowe (21/Jan/15 9:11 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand-plugin] (JENKINS-26288) Sauce connect remains running when test job is cancelled
Ross Rowe assigned JENKINS-26288 to Ross Rowe Sauce connect remains running when test job is cancelled Change By: Ross Rowe (14/Jan/15 8:11 AM) Assignee: KohsukeKawaguchi RossRowe This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand-plugin] (JENKINS-26288) Sauce connect remains running when test job is cancelled
Pasi Romo created JENKINS-26288 Sauce connect remains running when test job is cancelled Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: sauce-ondemand-plugin Created: 05/Jan/15 11:07 AM Description: I have noticed that in some occasions if the test job using sauce on demand plugin is interrupted manually at an early stage the sauce connect remains running even if the job gets cancelled. Here is an example log (shortened) of such a run: Launching Sauce Connect on server 02 Jan 13:53:46 - Sauce Connect 4.3.5, build 1588 c1405ab 02 Jan 13:53:46 - Using CA certificate bundle /etc/ssl/certs/ca-certificates.crt. 02 Jan 13:53:46 - Command line arguments: /home/jenkins/sc-4.3.5-linux/bin/sc 02 Jan 13:53:48 - Please wait for 'you may start your tests' to start your tests. 02 Jan 13:53:48 - Starting secure remote tunnel VM... Build was aborted Aborted by Jenkins user Incremented process count for test, now 1 Test reports were found but none of them are new. Did tests run? At this point: sauce connection is up and running even if there are no tests running internally jenkins has incremented the process count to 1 i.e. all the following builds will increment the process count based on this Eventually: the sauce connection won't get cleaned at any point by jenkins because the process count remains 1 i.e. jenkins won't shut down the sauce connection because it thinks there are tests running using it if the sauce connection is stopped out-side of jenkins (e.g. from sauce labs UI) all the following tests will fail because jenkins expects the sauce connect tunnel to exist since the incremented process count is maintained in some running java-process, at this point it seems that the only way to correct the situation is to e.g. re-boot the jenkins-server, which will clear the process count and following tests can start the sauce connect normally This problem occurs relatively rarely and is difficult to reproduce, but when it occurs can be problematic because of failing tests. Project: Jenkins Priority: Major Reporter: Pasi Romo This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
