[ https://issues.apache.org/jira/browse/MESOS-6949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16677498#comment-16677498 ]
Joseph Wu commented on MESOS-6949: ---------------------------------- Another fix: https://reviews.apache.org/r/69267/ > SchedulerTest.MasterFailover is flaky > ------------------------------------- > > Key: MESOS-6949 > URL: https://issues.apache.org/jira/browse/MESOS-6949 > Project: Mesos > Issue Type: Bug > Components: test > Environment: Observed on: > CentOS 7 VM, libevent and SSL enabled; > Ubuntu 14.04, cmake/clang, without libevent/SSL, on ASF CI > Reporter: Greg Mann > Assignee: Alexander Rukletsov > Priority: Major > Labels: flaky-test, tests > Fix For: 1.5.0 > > Attachments: MasterFailover-badrun.txt, > SchedulerTest.MasterFailover-on-ASF-CI.txt, SchedulerTest.MasterFailover.txt, > SchedulerTest_MasterFailover_1_badrun.txt > > > This was observed in a CentOS 7 VM, with libevent and SSL enabled: > {code} > W0118 22:38:33.789465 3407 scheduler.cpp:513] Dropping SUBSCRIBE: Scheduler > is in state DISCONNECTED > I0118 22:38:33.811820 3408 scheduler.cpp:361] Connected with the master at > http://127.0.0.1:43211/master/api/v1/scheduler > ../../src/tests/scheduler_tests.cpp:315: Failure > Mock function called more times than expected - returning directly. > Function call: connected(0x7fff97227550) > Expected: to be called once > Actual: called twice - over-saturated and active > {code} > Find attached the entire log from a failed run. -- This message was sent by Atlassian JIRA (v7.6.3#76005)