|
||||||||
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 am not sure it is the same cause, but I've got such hang. There is nothing in the job itself, but the system log has some relevant logs. The first seems to be:
Then some logs that are not related to the slave in question until
which is then followed by several instances of
with different X in "for X" in the first line and then
after which the slave never came back up. There were however these two errors:
that clearly refer to the failed slave further down the line.
The failed slave didn't seem to come up after trying to "Relaunch Slave Agent", after "Mark this node temporarily offline" followed by "Bring this node back online" and not even restarting the computer where the slave runs. In this it looks related to https://issues.jenkins-ci.org/browse/JENKINS-19465