You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Gavin (JIRA)" <ji...@apache.org> on 2019/04/29 09:27:21 UTC

[jira] [Issue Comment Deleted] (MESOS-8944) Get a callable object from `DROP_DISPATCH` so we can re-dispatch it.

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

Gavin updated MESOS-8944:
-------------------------
    Comment: was deleted

(was: www.rtat.net)

> Get a callable object from `DROP_DISPATCH` so we can re-dispatch it.
> --------------------------------------------------------------------
>
>                 Key: MESOS-8944
>                 URL: https://issues.apache.org/jira/browse/MESOS-8944
>             Project: Mesos
>          Issue Type: Task
>          Components: test
>            Reporter: Chun-Hung Hsiao
>            Priority: Major
>              Labels: integration, mesosphere
>
> If can get a callable object from {{DROP_DISPATCH}} (and maybe along with the target PID), then we could write tests as follows:
> {code}
> Future<Callable> toDispatch = DROP_DISPATCH(pid, &Some::member_function);
> AWAIT_READY(toDispatch);
> // Validate some state changes that happen after the member function is enqueued
> // but before it is executed.
> Future<Nothing> dispatched = dispatch(pid, toDispatch.get());
> AWAIT_READY(dispatched);
> // Validate some state changes that happen after the member function is executed.
> {code}
> This will make it easier to write tests against actors that we cannot control their progress.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)