|
||||||||
|
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.
I've had the patch running all day, and I've seen some job ABORTs still. My observation is that all the interrupthack logs that are printed show the same combination:
re-throwing valid InterruptedException 'null', count 1 (response false, chans closed in/out false/false, future null)
The way I interpret that is "no response yet, channels still open, and something about a future". I can't say I understand this code, but is the fact that future is null a problem at all? Could that value depend on the plugin that I use for my jobs? (multijob). Would the check be more accurate as (future != null && (future.isCancelled() || future.isDone()))?