[JIRA] [junit-plugin] (JENKINS-27931) stdout/stderr are truncated even on failing test

[andy.ja.lee@gmail.com (JIRA)]

Andrew Lee commented on JENKINS-27931

Re: stdout/stderr are truncated even on failing test About once a month one of our developers gets bitten by this and ends up banging their head against a wall trying to figure out why a log statement isn't showing up in the output. Even just making the message more obvious would be a big help (it's pretty hard to notice currently). Add Comment

This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)

[fly.beetle.cricket@gmail.com (JIRA)]

Fly Cricket commented on JENKINS-27931

Re: stdout/stderr are truncated even on failing test

Same problem here. It does not make too much sense to hide the test's standard and error output. When using Gradle, the console log is also quite empty. So there's no workaround to get the desired information.

Add Comment

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

[regs@akom.net (JIRA)]

Alexander Komarov commented on JENKINS-27931

Re: stdout/stderr are truncated even on failing test

WORKAROUND for me has been to archive the XML in addition to publishing it.  Not ideal, but it has worked well.   Also, In pipeline jobs, I have fancier logic to make this less ugly. It does the following: Publishes XML via the JUnit plugin (normally), ie:  junit allowEmptyResults: true, testResults: '/TEST-.xml'* Deletes any successful junit XML (I have a pipeline library method to scan files for failures="0" and errors="0", omitting code for brevity).   This is optional and is done to conserve disk space. Zips and archives the original glob which is now only failure files: zip archive: true, dir: '', glob: '/TEST-.xml', zipFile: junit-failures-xml.zip* Hope this helps.

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[info@petervoss.org (JIRA)]

Peter Voß commented on JENKINS-27931

Re: stdout/stderr are truncated even on failing test

Could one make the character threshold configurable? Showing the stdout is such a nice feature, but it turns out to be mostly useless, if it does not cover the relevant tests. I typically only see the output of about 6 tests (of about more than 20) in the output. But typically not the output of the failing tests. To me it seems that the hard coded value of 50.000 (if I am not mistaken) could easily be increased a lot on most systems to not cause major problems. I'd rather invest in more hdd space than not having relevant information at hand.

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)