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

Timothy Chen commented on MESOS-4348:
-------------------------------------

commit 764e3532f5116305ca0d6dd1053b4a4041a8abbb
Author: Anand Mazumdar <[email protected]>
Date:   Thu Jan 14 14:58:36 2016 -0800

    Fixed gmock warnings in hook tests.

    We did not have an expectation on the `shutdown` method of the 
`MockExecutor`.
    This led to the gmock warning being emitted in some runs.

    The tests that are being fixed are:

    - `HookTest.VerifyMasterLaunchTaskHook`
    - `HookTest.VerifySlaveRunTaskHook`
    - `HookTest.VerifySlaveTaskStatusDecorator`

    Review: https://reviews.apache.org/r/42216/

> GMock warning in HookTest.VerifySlaveRunTaskHook, 
> HookTest.VerifySlaveTaskStatusDecorator
> -----------------------------------------------------------------------------------------
>
>                 Key: MESOS-4348
>                 URL: https://issues.apache.org/jira/browse/MESOS-4348
>             Project: Mesos
>          Issue Type: Bug
>          Components: tests
>            Reporter: Neil Conway
>            Priority: Minor
>              Labels: mesosphere, tests
>             Fix For: 0.27.0
>
>
> {noformat}
> [ RUN      ] HookTest.VerifySlaveRunTaskHook
> GMOCK WARNING:
> Uninteresting mock function call - returning directly.
>     Function call: shutdown(0x7ff079cb2420)
> Stack trace:
> [       OK ] HookTest.VerifySlaveRunTaskHook (51 ms)
> [ RUN      ] HookTest.VerifySlaveTaskStatusDecorator
> GMOCK WARNING:
> Uninteresting mock function call - returning directly.
>     Function call: shutdown(0x7ff079cbb790)
> Stack trace:
> [       OK ] HookTest.VerifySlaveTaskStatusDecorator (54 ms)
> {noformat}
> Occurs non-deterministically for me. OSX 10.10.



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

Reply via email to