This is a pretty old issue, and doesn't look like it's had any activity. I run into this error rather frequently for jobs running on slaves > 5 hours. Is there a known work around? We have a work order to investigate fixing it, but that would be foolish if there's already a solution.

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

Reply via email to