[JIRA] (JENKINS-51409) SauceConnect PID Not Being Removed

2018-05-18 Thread sam.schi...@discounttire.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Schiavo updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51409  
 
 
  SauceConnect PID Not Being Removed   
 

  
 
 
 
 

 
Change By: 
 Sam Schiavo  
 
 
Issue Type: 
 Bug Task  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-51409) SauceConnect PID Not Being Removed

2018-05-18 Thread sam.schi...@discounttire.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Schiavo resolved as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 This issue has been resolved. The jobs that were failing had the "Enable SauceConnect" button checked, so it was trying to establish a tunnel when one was already in place. When I unchecked this box, the jobs completed with no issues.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-51409  
 
 
  SauceConnect PID Not Being Removed   
 

  
 
 
 
 

 
Change By: 
 Sam Schiavo  
 
 
Status: 
 Open Resolved  
 
 
Assignee: 
 Yeh Fang Sam Schiavo  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

[JIRA] (JENKINS-51409) SauceConnect PID Not Being Removed

2018-05-18 Thread sam.schi...@discounttire.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Schiavo commented on  JENKINS-51409  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SauceConnect PID Not Being Removed   
 

  
 
 
 
 

 
 This issue has been resolved. I found that all the jobs had the "Enable SauceConnect" box checked, which would try to open a tunnel when one was already opened. When I uncheck this box, the jobs run with no issues through the tunnel that is already set up and configured.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-51409) SauceConnect PID Not Being Removed

2018-05-17 Thread sam.schi...@discounttire.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Schiavo created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51409  
 
 
  SauceConnect PID Not Being Removed   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Yeh Fang  
 
 
Attachments: 
 sc.log  
 
 
Components: 
 sauce-ondemand-plugin  
 
 
Created: 
 2018-05-17 21:14  
 
 
Environment: 
 Jenkins version 2.118  Sauce OnDemand plugin version 1.175  
 
 
Labels: 
 plugin jenkins sauce-connect SauceOnDemand  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Sam Schiavo  
 

  
 
 
 
 

 
 When we run a SauceConnect job, it leaves the process running so the PID file is never removed. The next job tries to run and gets the error message "Error creating pidfile /tmp/sc_client.pid: resource temporarily unavailable" I can manually kill the process, remove the sc_client.pid file, then start the job and it runs with no issues. At the end of the job that runs correctly, there is a java error, but I'm not sure if it is related or not. Finished post-build for Sauce Labs plugin Starting Sauce Labs test publisher Finished Sauce Labs test publisher ERROR: Build step failed with exception java.lang.NullPointerException     at hudson.plugins.sauce_ondemand.SauceOnDemandReportPublisher.processBuildOutput(SauceOnDemandReportPublisher.java:349)     at hudson.plugins.sauce_ondemand.SauceOnDemandReportPublisher.getTestData(SauceOnDemandReportPublisher.java:162)     at