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




src/tests/group_tests.cpp (lines 450 - 454)
<https://reviews.apache.org/r/43035/#comment180632>

    Can you explain why you needed to move this?



src/tests/group_tests.cpp (line 483)
<https://reviews.apache.org/r/43035/#comment180633>

    backticks for GroupProcess?



src/tests/group_tests.cpp (line 490)
<https://reviews.apache.org/r/43035/#comment180634>

    Do you mean `Ensure that no pending messages are delivered.`?
    Or `if any`, then what?


- Joris Van Remoortere


On Feb. 1, 2016, 9:40 p.m., Neil Conway wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43035/
> -----------------------------------------------------------
> 
> (Updated Feb. 1, 2016, 9:40 p.m.)
> 
> 
> Review request for mesos and Joris Van Remoortere.
> 
> 
> Repository: mesos
> 
> 
> Description
> -------
> 
> Check that even though we might fire a timer for a `GroupProcess` that has 
> been
> destroyed, this does not result in dispatching an event to a reclaimed 
> process.
> 
> 
> Diffs
> -----
> 
>   src/tests/group_tests.cpp 6344fade519f47cd4ac3a2dc36c3237d9adf4cf8 
> 
> Diff: https://reviews.apache.org/r/43035/diff/
> 
> 
> Testing
> -------
> 
> `make check; ./src/mesos-tests --gtest_filter="GroupTest.TimerCleanup" 
> --gtest_repeat=4000 --gtest_break_on_failure`
> 
> I also verified that if you remove the `delete` of the `GroupProcess`, the 
> test fails because the `expired` callback is invoked (the `Clock::settle()` 
> is necessary to ensure that this happens).
> 
> 
> Thanks,
> 
> Neil Conway
> 
>

Reply via email to