|
||||||||
|
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/d/optout.
There is no relevant logging. Fixing this would really hinge on finding a fully reproducible test case.
Or, someone with detailed knowledge of jzlib would need to inject low-level diagnostics, as we did for JENKINS-20618 and JENKINS-20114. Unfortunately an EOFException is very generic and I cannot think of a diagnostic other than capturing the entire stream to that point, which would be unacceptable from a performance standpoint. (How large are your artifacts?)
It would be nice to use the standard gzip support in the JRE. Unfortunately, that seems to cause occasional 100% CPU freezes that were a major issue for many Jenkins users (worse than issues like this).