-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/22313/#review45350
-----------------------------------------------------------


Looks great. Just a couple of comments from me, and then I'll let Vinod/Ian 
give the final shepherd seal of approval.


src/slave/slave.cpp
<https://reviews.apache.org/r/22313/#comment80165>

    Am I blind? Where does 'executor' come from? You have executorId to start 
with, and it's not until later in this function that "Executor* executor = 
framework->getExecutor(executorId);"
    Maybe you should pass the containerId as a parameter as well, in case the 
executor exited before your containerizer->update() future failed.



src/slave/slave.cpp
<https://reviews.apache.org/r/22313/#comment80166>

    s/statsu/status/



src/tests/slave_tests.cpp
<https://reviews.apache.org/r/22313/#comment80168>

    First, AWAIT_READY(offers2);


- Adam B


On June 11, 2014, 1:50 a.m., Yifan Gu wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/22313/
> -----------------------------------------------------------
> 
> (Updated June 11, 2014, 1:50 a.m.)
> 
> 
> Review request for mesos, Ian Downes and Vinod Kone.
> 
> 
> Bugs: MESOS-886
>     https://issues.apache.org/jira/browse/MESOS-886
> 
> 
> Repository: mesos-git
> 
> 
> Description
> -------
> 
> Added __runTask() to wait for the completion of containerizer->update() and 
> check the result before sending RunTaskMessage.
> 
> 
> Diffs
> -----
> 
>   src/slave/slave.hpp 34687e5 
>   src/slave/slave.cpp 643c088 
>   src/tests/slave_tests.cpp 2c8f183 
> 
> Diff: https://reviews.apache.org/r/22313/diff/
> 
> 
> Testing
> -------
> 
> SlaveTest, CancelTaskIfContainerizerFails
> 
> Which tests that if the containerizer->update() return a Failure, the task 
> won't be launched and the scheduler will get TASK_LOST.
> 
> make check
> 
> 
> Thanks,
> 
> Yifan Gu
> 
>

Reply via email to