[
https://issues.apache.org/jira/browse/OOZIE-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16625805#comment-16625805
]
Andras Piros commented on OOZIE-3343:
-------------------------------------
Looks much better [~kmarton]! Now I can see the one failing test in the test
output :) nice job!
A couple of nits:
- please take care of too long lines
- wording: *Tests errors* should be *Tests in error*, and *Tests timeouts*
should be *Tests timed out*
> [build] [tests] Add the first five test errors per module to the report
> -----------------------------------------------------------------------
>
> Key: OOZIE-3343
> URL: https://issues.apache.org/jira/browse/OOZIE-3343
> Project: Oozie
> Issue Type: Bug
> Components: build, tests
> Affects Versions: 5.0.0
> Reporter: Julia Kinga Marton
> Assignee: Julia Kinga Marton
> Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-3343-001.patch, OOZIE-3343-002.patch,
> OOZIE-3343-003.patch, OOZIE-3343-004.patch, OOZIE-3343-005.patch,
> OOZIE-3343-DEBUG_PURPOSE_DO_NOT_MERGE2.patch
>
>
> After fixing the false positive precommit reports in OOZIE-3317, if there are
> some kind of errors during junit execution, the following information is
> printed out:
> {color:#FF0000}-1 TESTS{color}
> There were errors during execution. Check console output for details.
> It should be useful to have the concrete errors printed out as well. In order
> to avoid the very long reports in case of lots of failures, we should limit
> the printed out errors to a specific number (5)/module.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
