[
https://issues.apache.org/jira/browse/OOZIE-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15994602#comment-15994602
]
Andras Piros commented on OOZIE-2815:
-------------------------------------
[~satishsaley] [~puru] I can also state that following tests are flaky
(actually, most of the time failing) on upstream master:
{noformat}
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Concurrency config is parallel='classes', perCoreThreadCount=false,
threadCount=1, useUnlimitedThreads=false
objc[83029]: Class JavaLaunchHelper is implemented in both
/Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/jre/bin/java
(0x1020494c0) and
/Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/jre/lib/libinstrument.dylib
(0x10d0274e0). One of the two will be used. Which one is undefined.
Running org.apache.oozie.util.TestTimestampedMessageParser
Tests run: 4, Failures: 1, Errors: 2, Skipped: 0, Time elapsed: 37.865 sec <<<
FAILURE!
Results :
Failed tests:
testNofindLogs(org.apache.oozie.util.TestTimestampedMessageParser): should not
throw Exception
Tests in error:
testProcessRemainingLog(org.apache.oozie.util.TestTimestampedMessageParser)
testProcessRemainingCoordinatorLogForActions(org.apache.oozie.util.TestTimestampedMessageParser)
Tests run: 4, Failures: 1, Errors: 2, Skipped: 0
{noformat}
> Oozie not always display job log
> --------------------------------
>
> Key: OOZIE-2815
> URL: https://issues.apache.org/jira/browse/OOZIE-2815
> Project: Oozie
> Issue Type: Bug
> Reporter: Purshotam Shah
> Assignee: Satish Subhashrao Saley
> Fix For: 5.0.0
>
> Attachments: OOZIE-2815-amend-1.patch, OOZIE-2815-V2.patch,
> OOZIE-2815-V3.patch, OOZIE-2815-V4.patch, OOZIE-2815-V5.patch
>
>
> There are few issues with log streaming. We will fix following things.
> 1. UI has an issue with displaying "loading... done". It used to show loading
> done even if logs were not loaded entirely.
> 2. Server-server communication time out. The default time is 1 min. Setting
> to 3 min same as UI.
> 3. We use to throw an error message if log scan duration is more than
> configured duration. We will be truncating log.
> 4. No log scan duration check for audit and error log since it doesn't
> support log filter.
> 5. Different buffer.len setting for error and audit log, so that partial
> loading can be faster.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
