You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Julia Kinga Marton (JIRA)" <ji...@apache.org> on 2018/09/12 13:00:00 UTC
[jira] [Updated] (OOZIE-3343) [build] Add the first x errors per
module in case of junit errors to the precommit report
[ https://issues.apache.org/jira/browse/OOZIE-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julia Kinga Marton updated OOZIE-3343:
--------------------------------------
Summary: [build] Add the first x errors per module in case of junit errors to the precommit report (was: [build] Add the first 5 errors per module in case of junit errors)
> [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
>
> 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)