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

Andras Piros commented on OOZIE-3343:
-------------------------------------

[~kmarton] it seems to me that the latest {{patch 004}} based test run [gives 
following test 
error|https://builds.apache.org/job/PreCommit-OOZIE-Build/850/consoleFull]:
{noformat}
[ERROR] Errors: 
[ERROR] 
org.apache.oozie.service.TestCallableQueueService.testPriorityExecutionOrder(org.apache.oozie.service.TestCallableQueueService)
[ERROR]   Run 1: TestCallableQueueService.testPriorityExecutionOrder:993 » 
ConcurrentModification
[ERROR]   Run 2: TestCallableQueueService.testPriorityExecutionOrder:993 » 
ConcurrentModification
[INFO] 
[WARNING] Flakes: 
[WARNING] 
org.apache.oozie.command.coord.TestCoordActionsKillXCommand.testActionKillCommandDate(org.apache.oozie.command.coord.TestCoordActionsKillXCommand)
[ERROR]   Run 1: TestCoordActionsKillXCommand.testActionKillCommandDate:131 
expected:<RUNNING> but was:<KILLED>
[INFO]   Run 2: PASS
{noformat}

Can you please have a look why:
- there are no test runs marked as erroneous but 
{{TestCallableQueueService#testPriorityExecutionOrder()}} should be
- three times lines are too long inside {{bin/test-patch-20-tests}}

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

Reply via email to