[ 
https://issues.apache.org/jira/browse/OOZIE-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16617434#comment-16617434
 ] 

Julia Kinga Marton commented on OOZIE-3343:
-------------------------------------------

*1. No test failure, no error, no timeout*

{color:green}+1 TESTS{color}
 . Tests run: 1424

*2. No test failures, no test errors, but one timeout*

{color:red}-1 TESTS{color}
 . Tests run : 1424
 . Tests failed : 0
 . Tests errors : 0
 . Tests timeouts : 1

Check consolt output for the full list of errors/failures

*3. timeout+failures+errors*

{color:red}-1 TESTS{color}
 . Tests run : 1424
 . Tests failed : 10
 . Tests errors : 9
 . Tests timeouts : 1

[ERROR] There are [10] test failures in [client].
 The first 5 failures are:
 testParseWorkflowAction(org.apache.oozie.client.rest.TestJsonToBean)
 testParseWorkflowActions(org.apache.oozie.client.rest.TestJsonToBean)
 testParseWorkflowJob(org.apache.oozie.client.rest.TestJsonToBean)
 testParseWorkflowJobs(org.apache.oozie.client.rest.TestJsonToBean)
 testNullDateStr(org.apache.oozie.client.rest.TestJsonUtils)

[ERROR] There are [3] test errors in [client].
 The first 5 errors are:
 testValidatePrintCoordJobMethodOutput(org.apache.oozie.cli.TestOozieCLIMethods)
 testValidatePrintJobOutput(org.apache.oozie.cli.TestOozieCLIMethods)
 testValidatePrintWorkflowActionOutput(org.apache.oozie.cli.TestOozieCLIMethods)
 [ERROR] There are [6] test errors in [sharelib].
 The first 5 errors are:
 
testHandlingWhenArgsContainNullsAndNullsNotAllowed(org.apache.oozie.action.hadoop.TestLauncherAMUtils)
 
testArgsHandlingWhenArgsContainsNullsOnlyAndNullsNotAllowed(org.apache.oozie.action.hadoop.TestLauncherAMUtils)
 
testHandlingWhenArgsContainNullsAndNullAllowed(org.apache.oozie.action.hadoop.TestLauncherAMUtils)
 
testArgsHandlingWhenArgsContainsOneNullAndNullsAllowed(org.apache.oozie.action.hadoop.TestLauncherAMUtils)
 
testArgsHandlingWhenArgsContainsOneNullAndNullsNotAllowed(org.apache.oozie.action.hadoop.TestLauncherAMUtils)

Check console output for the full list of errors/failures

> [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
>
>
> 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)

Reply via email to