|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

We have the same problem with one of our slaves running CentOS 6.3 64 bit and jenkins version 1.481. Interestingly enough though the first two jobs I moved to this slave did not show this problem. My stack trace has slightly different line numbers:
Anything anybody wants me to do in order to figure out the cause of this?