Hi all,

Just to inform you that we did have this issue with some of our jobs with Jenkins ver. 1.517 and Jenkins ver. 1.537.
We did some maintenance tasks:

  • We increased the size of the temporary space of the master.
  • We synchronized some of our slave's clock using ntp.

Since those maintenance tasks, a month ago, we no more see this issue. I do not know if this is related.

Hope this help!

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/groups/opt_out.

Reply via email to