mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Rukletsov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MESOS-6949) SchedulerTest.MasterFailover is flaky
Date Wed, 08 Nov 2017 17:36:00 GMT

     [ https://issues.apache.org/jira/browse/MESOS-6949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alexander Rukletsov updated MESOS-6949:
---------------------------------------
    Sprint: Mesosphere Sprint 68

> 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
>              Labels: flaky-test, tests
>         Attachments: MasterFailover-badrun.txt, SchedulerTest.MasterFailover-on-ASF-CI.txt,
SchedulerTest.MasterFailover.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
(v6.4.14#64029)

Mime
View raw message