[jira] [Comment Edited] (MESOS-1013) ExamplesTest.JavaLog is flaky

["Greg Mann (JIRA)" <ji...@apache.org>]

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

Greg Mann edited comment on MESOS-1013 at 8/14/15 6:49 PM:
-----------------------------------------------------------

Created a new ticket for the more general issue regarding the lack of synchronization between the JVM and native shutdown routines: MESOS-3264


was (Author: greggomann):
Created a new ticket for the more general issue regarding the lack of synchronization between the JVM and native routines: MESOS-3264

> ExamplesTest.JavaLog is flaky
> -----------------------------
>
>                 Key: MESOS-1013
>                 URL: https://issues.apache.org/jira/browse/MESOS-1013
>             Project: Mesos
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 0.19.0
>            Reporter: Vinod Kone
>            Assignee: Greg Mann
>              Labels: flaky, mesosphere
>         Attachments: ExamplesTest.JavaLog.logs
>
>
> The {{ExamplesTest.JavaLog}} test framework is flaky, possibly related to a race condition between mutexes.
> {noformat}
> [ RUN      ] ExamplesTest.JavaLog
> Using temporary directory '/tmp/ExamplesTest_JavaLog_WBWEb9'
> Feb 18, 2014 12:10:57 PM TestLog main
> INFO: Starting a local ZooKeeper server
> ...
> F0218 12:10:58.575036 17450 coordinator.cpp:394] Check failed: !missing Not expecting local replica to be missing position 3 after the writing is done
> *** Check failure stack trace: ***
> tests/script.cpp:81: Failure
> Failed
> java_log_test.sh terminated with signal 'Aborted'
> [  FAILED  ] ExamplesTest.JavaLog (2166 ms)
> {noformat}
> Full logs attached.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)