[jira] [Updated] (MESOS-6949) SchedulerTest.MasterFailover is flaky
[
https://issues.apache.org/jira/browse/MESOS-6949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rukletsov updated MESOS-6949:
---
Shepherd: James Peach (was: Vinod Kone)
> 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
> Fix For: 1.5.0
>
> 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)
[jira] [Updated] (MESOS-6949) SchedulerTest.MasterFailover is flaky
[
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)
[jira] [Updated] (MESOS-6949) SchedulerTest.MasterFailover is flaky
[
https://issues.apache.org/jira/browse/MESOS-6949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rukletsov updated MESOS-6949:
---
Shepherd: Vinod Kone
Story Points: 2
> 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)
[jira] [Updated] (MESOS-6949) SchedulerTest.MasterFailover is flaky
[
https://issues.apache.org/jira/browse/MESOS-6949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rukletsov updated MESOS-6949:
---
Attachment: MasterFailover-badrun.txt
> 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
> 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)
[jira] [Updated] (MESOS-6949) SchedulerTest.MasterFailover is flaky
[
https://issues.apache.org/jira/browse/MESOS-6949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rukletsov updated MESOS-6949:
---
Labels: flaky-test tests (was: tests)
> 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
> Labels: flaky-test, tests
> Attachments: 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)
[jira] [Updated] (MESOS-6949) SchedulerTest.MasterFailover is flaky
[
https://issues.apache.org/jira/browse/MESOS-6949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Mann updated MESOS-6949:
-
Attachment: SchedulerTest.MasterFailover.txt
> SchedulerTest.MasterFailover is flaky
> -
>
> Key: MESOS-6949
> URL: https://issues.apache.org/jira/browse/MESOS-6949
> Project: Mesos
> Issue Type: Bug
> Components: tests
> Environment: CentOS 7 VM, libevent and SSL enabled
>Reporter: Greg Mann
> Labels: tests
> Attachments: 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.3.4#6332)
