![]() |
|
|
|
|
Change By:
|
Alex V
(14/Apr/15 1:49 PM)
|
|
Description:
|
A test class with many tests in it may produce "large" logs on stdout. In that case, if there is a test failing within this test class, I would have expected that the entire stdout output is kept by junit plugin.
But it is truncated.
{code}
...[truncated 1051034 chars]...
{code}
This seems to be voluntary: https://github.com/jenkinsci/junit-plugin/commit/5f7513baff89516cd7217ea39101ad67116cd059
I totally understand the need of discard data for tests succeed. However for failing tests, it makes almost impossible to find the cause of failure.
Besides, it contradicts the documentation of the option {{Retain long standard output/error}} which states:
{panel}
If checked, any standard output or error from a test suite will be retained in the test results after the build completes. (This refers only to additional messages printed to console, not to a failure stack trace.) {color:red}Such output is always kept if the test failed{color}, but by default lengthy output from passing tests is truncated to save space. Check this option if you need to see every log message from even passing tests, but beware that Jenkins's memory consumption can substantially increase as a result, even if you never look at the test results!
{panel}
Is that possible to at least make this configurable
.
?
In my workflow, the ideal would be to completely discard passing tests logs, and keep all of failing ones.
|
|
|
|
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.
