After a lot of investigation, I now have a way to reliably reproduce this
error, and can avoid it. The issue occurs when Jenkins tries to abort the
job during JBehave testing. It originally occurred when someone manually
aborted a job, but became consistent when I enabled a Jenkins plugin that
I am not running the build on the master. They run on a separate slave.
Thanks for the suggestion to look for a ticket in the issue tracker for the
plugin. I'll try that.
Jeff
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe fr
I have a Jenkins job running some JBehave tests. The job fails, but isn't
listed in the build queue any more. Unfortunately, it appears to have
spawned a thread that is stuck in an infinite loop. It keeps throwing an
interrupt exception, printing a stack trace, and then doing it again. The
prob
