|
||||||||
|
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/d/optout.
Could you please do the following:
1. On the Jenkins master, go to a build showing this behavior. (JENKINS_HOME/jobs/jobname/builds/2014-xx-yy_zz-ww-vv/), create a backup of the buildlog, and open the real one (original file name) in a text editor.
2. Do kind of a "binary search" for the location where it breaks by deleting the first or second half of the contents, saving, and reloading the log page in Jenkins. If it still occurs, repeat. Otherwise, delete the rest and insert the previously deleted half (easiest by working with the clipboard, just cut it rather than deleting), and reload Jenkins to see whether than second half breaks log display.
3. Repeat until you've isolated a small enough sample (no more than 10KB or so would be great), and post that.
Please note that console annotations (what makes text show up bold) look like garbage between escape chars. So 1. use a real text editor, not notepad, to slice the file and 2. keep those annotations intact.