[
https://issues.apache.org/jira/browse/MESOS-3486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15146770#comment-15146770
]
Michael Browning commented on MESOS-3486:
-----------------------------------------
Actually, this holds for DROP_PROTOBUF (which also invokes FutureProtobuf) in a
number of cases too, viz:
Future<Message> registerExecutorMessage =
DROP_MESSAGE(Eq(RegisterExecutorMessage().GetTypeName()), _, _);
DROP_PROTOBUF would return an RegisterExecutorMessage, which is a subclass of
::google::protobuf::Message, and not an instance of process::Message.
> Use DROP_PROTOBUF instead of DROP_MESSAGE in tests
> --------------------------------------------------
>
> Key: MESOS-3486
> URL: https://issues.apache.org/jira/browse/MESOS-3486
> Project: Mesos
> Issue Type: Improvement
> Reporter: Neil Conway
> Assignee: Michael Browning
> Priority: Trivial
> Labels: mesosphere, newbie, tests
>
> The tests use DROP_MESSAGE(), DROP_MESSAGES(), and FUTURE_MESSAGE() in
> various places where it would be more clear and concise to use
> DROP_PROTOBUF(), DROP_PROTOBUFS(), and FUTURE_PROTOBUF() instead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
