[
https://issues.apache.org/jira/browse/OOZIE-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16621999#comment-16621999
]
Julia Kinga Marton commented on OOZIE-3343:
-------------------------------------------
The cause of the false +1 report is that, in OOZIE-332, during distro analysis,
the maven command was extended with performing a clean, so all the surefire
reports generated by the tests are deleted, and when the test report is
created, it will find no errors and warnings, so even if there were failures,
it reports +1 for the tests.
> [build] Add the first x errors per module in case of junit errors to the
> precommit report
> -----------------------------------------------------------------------------------------
>
> Key: OOZIE-3343
> URL: https://issues.apache.org/jira/browse/OOZIE-3343
> Project: Oozie
> Issue Type: Bug
> Components: scripts
> Affects Versions: 5.0.0
> Reporter: Julia Kinga Marton
> Assignee: Julia Kinga Marton
> Priority: Major
> Attachments: OOZIE-3343-001.patch,
> OOZIE-3343-DEBUG_PURPOSE_DO_NOT_MERGE.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)
