mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kone (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MESOS-3339) Implement filtering mechanism for (Scheduler API Events) Testing
Date Tue, 16 Feb 2016 18:12:18 GMT

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

Vinod Kone updated MESOS-3339:
------------------------------
    Sprint: Mesosphere Sprint 20, Mesosphere Sprint 21, Mesosphere Sprint 22, Mesosphere Sprint
29  (was: Mesosphere Sprint 20, Mesosphere Sprint 21, Mesosphere Sprint 22)

> Implement filtering mechanism for (Scheduler API Events) Testing
> ----------------------------------------------------------------
>
>                 Key: MESOS-3339
>                 URL: https://issues.apache.org/jira/browse/MESOS-3339
>             Project: Mesos
>          Issue Type: Task
>          Components: test
>            Reporter: Anand Mazumdar
>            Assignee: Anand Mazumdar
>              Labels: mesosphere
>
> Currently, our testing infrastructure does not have a mechanism of filtering/dropping
HTTP events of a particular type from the Scheduler API response stream.  We need a {{DROP_HTTP_CALLS}}
abstraction that can help us to filter a particular event type.
> {code}
> // Enqueues all received events into a libprocess queue.
> ACTION_P(Enqueue, queue)
> {
>   std::queue<Event> events = arg0;
>   while (!events.empty()) {
>     // Note that we currently drop HEARTBEATs because most of these tests
>     // are not designed to deal with heartbeats.
>     // TODO(vinod): Implement DROP_HTTP_CALLS that can filter heartbeats.
>     if (events.front().type() == Event::HEARTBEAT) {
>       VLOG(1) << "Ignoring HEARTBEAT event";
>     } else {
>       queue->put(events.front());
>     }
>     events.pop();
>   }
> }
> {code}
> This helper code is duplicated in at least two places currently, Scheduler Library/Maintenance
Primitives tests. 
> - The solution can be as trivial as moving this helper function to a common test-header.
> - Implement a {{DROP_HTTP_CALLS}} similar to what we do for other protobufs via {{DROP_CALLS}}.



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

Mime
View raw message