|
||||||||
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.
I had no browser selected. Explained in description why.
Indeed the above were from version 1.113 where it also happened once immediately after downgrade (probably because of a 'sc <defunct>' process).
Anyway here it is from when I had it running with 1.125, then it started to fail again:
At 16:34 there was a successful run of the job.
At 18:34 the tests failed because of a problem with our app. server not starting and thus the unit tests could not connect to it; unit tests connect of 2 min timed out and the job failed.
At 19:14:35 I now see two jobs started simultaneously (one by a timer the other by a colleague manually starting it in the same second)! One succeeded and one failed with that error in console "Process count non-zero, but no active tunnels found - Process count reset to zero - FATAL: Unable to start Sauce Connect, please see the Sauce Connect log"
That should have been possible as the 2 jobs are configured to be mutually exclusive (using another plugin for that) and never saw them run at the same time before even if I started them both manually one after the other.
But anyway it still shouldn't make sauce plugin non-functional for all future jobs... All future jobs failed until I downgraded and killed processes.