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

haosdent updated MESOS-1640:
----------------------------
    Labels: flaky health-check mesosphere  (was: flaky mesosphere)

> HealthCheckTests are flaky under gprof/gcov
> -------------------------------------------
>
>                 Key: MESOS-1640
>                 URL: https://issues.apache.org/jira/browse/MESOS-1640
>             Project: Mesos
>          Issue Type: Bug
>          Components: test
>            Reporter: Dominic Hamon
>            Assignee: Timothy Chen
>            Priority: Minor
>              Labels: flaky, health-check, mesosphere
>
> When running {{/support/coverage.sh}} the {{HealthCheckTest}} fixture 
> exhibits multiple flakes:
> {noformat}
> [ RUN      ] HealthCheckTest.HealthyTask
> ../../src/tests/health_check_tests.cpp:165: Failure
> Value of: statusRunning.get().state()
>   Actual: TASK_FAILED
> Expected: TASK_RUNNING
> ../../src/tests/health_check_tests.cpp:167: Failure
> Failed to wait 10secs for statusHealth
> ../../src/tests/health_check_tests.cpp:158: Failure
> Actual function call count doesn't match EXPECT_CALL(sched, 
> statusUpdate(&driver, _))...
>          Expected: to be called twice
>            Actual: called once - unsatisfied and active
> [  FAILED  ] HealthCheckTest.HealthyTask (11854 ms)
> [ RUN      ] HealthCheckTest.EnvironmentSetup
> ../../src/tests/health_check_tests.cpp:314: Failure
> Value of: statusRunning.get().state()
>   Actual: TASK_FAILED
> Expected: TASK_RUNNING
> ../../src/tests/health_check_tests.cpp:316: Failure
> Failed to wait 10secs for statusHealth
> ../../src/tests/health_check_tests.cpp:307: Failure
> Actual function call count doesn't match EXPECT_CALL(sched, 
> statusUpdate(&driver, _))...
>          Expected: to be called twice
>            Actual: called once - unsatisfied and active
> [  FAILED  ] HealthCheckTest.EnvironmentSetup (12020 ms)
> {noformat}



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

Reply via email to