mesos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dominic Hamon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-1341) AllocatorZooKeeperTest/0.FrameworkReregistersFirst is flaky
Date Mon, 16 Jun 2014 17:58:03 GMT

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

Dominic Hamon commented on MESOS-1341:
--------------------------------------

commit a8c8b89638bb9897ede7d36d3f5c02d9d79c7b46
Author: Dominic Hamon <dhamon@twopensource.com>
Commit: Vinod Kone <vinod@twitter.com>

    Enabling ZooKeeper tests that were previously disabled.
    
    Review: https://reviews.apache.org/r/22591

commit d3376b677638166628ef54e30652f2607951d0ed
Author: Vinod Kone <vinod@twitter.com>
Commit: Vinod Kone <vinod@twitter.com>

    Fixed ZooKeeperProcess and ProcessWatcher to avoid deadlock during ZooKeeperProcess termination.
    
    Review: https://reviews.apache.org/r/22521


> AllocatorZooKeeperTest/0.FrameworkReregistersFirst is flaky
> -----------------------------------------------------------
>
>                 Key: MESOS-1341
>                 URL: https://issues.apache.org/jira/browse/MESOS-1341
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: Jie Yu
>             Fix For: 0.20.0
>
>
> centos6 gcc44
> [ RUN      ] AllocatorZooKeeperTest/0.FrameworkReregistersFirst
> ../../../mesos/src/tests/allocator_zookeeper_tests.cpp:151: Failure
> Failed to wait 10secs for resourceOffers2
> ../../../mesos/src/tests/allocator_zookeeper_tests.cpp:140: Failure
> Actual function call count doesn't match EXPECT_CALL(allocator2, slaveAdded(_, _, _))...
>          Expected: to be called once
>            Actual: never called - unsatisfied and active
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGSEGV (0xb) at pc=0x00007f9255f4c8bc, pid=9533, tid=140266265978624
> #
> # JRE version: OpenJDK Runtime Environment (7.0-b31) (build 1.7.0-u45-b31-rel_22)
> # Java VM: OpenJDK 64-Bit Server VM (24.45-b08 mixed mode linux-amd64 compressed oops)
> # Problematic frame:
> # C  [libmesos-0.19.0.so+0x6918bc]  void process::dispatch<mesos::internal::master::allocator::AllocatorProcess,
mesos::SlaveID const&, mesos::SlaveInfo const&, hashmap<mesos::FrameworkID, mesos::Resources>
const&, mesos::SlaveID, mesos::SlaveInfo, hashmap<mesos::FrameworkID, mesos::Resources>
>(process::Process<mesos::internal::master::allocator::AllocatorProcess> const*,
void (mesos::internal::master::allocator::AllocatorProcess::*)(mesos::SlaveID const&,
mesos::SlaveInfo const&, hashmap<mesos::FrameworkID, mesos::Resources> const&),
mesos::SlaveID, mesos::SlaveInfo, hashmap<mesos::FrameworkID, mesos::Resources>)+0x8c
> #
> # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try
"ulimit -c unlimit
> ed" before starting Java again
> #
> # An error report file with more information is saved as:
> # /tmp/AllocatorZooKeeperTest_0_FrameworkReregistersFirst_syk46I/hs_err_pid9533.log
> ## If you would like to submit a bug report, please visit:#   http://bugreport.sun.com/bugreport/crash.jsp#



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message