-
Task
-
Resolution: Not A Defect
-
Minor
-
Jenkins version 2.118
Sauce OnDemand plugin version 1.175
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 hudson.plugins.sauce_ondemand.SauceOnDemandTestPublisher.addTestDataPublishersToBuildReport(SauceOnDemandTestPublisher.java:192)
at hudson.plugins.sauce_ondemand.SauceOnDemandTestPublisher.perform(SauceOnDemandTestPublisher.java:98)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744)
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690)
at hudson.model.Build$BuildExecution.post2(Build.java:186)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635)
at hudson.model.Run.execute(Run.java:1819)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:429)
Build step 'Run Sauce Labs Test Publisher' marked build as failure
I have added the sc.log to the ticket from the master node.
Please let me know if there are any more info that you need.
[JENKINS-51409] SauceConnect PID Not Being Removed
Sam Schiavo
added a comment - 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.
Sam Schiavo
added a comment - 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. 
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.