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



src/tests/cgroups_tests.cpp (line 991)
<https://reviews.apache.org/r/36605/#comment146234>

    I wonder what is the follow up action around this TODO? Seems like it 
stated why we commented the code but not anything we should do in the future?



src/tests/perf_tests.cpp (line 172)
<https://reviews.apache.org/r/36605/#comment146235>

    ditto


- Timothy Chen


On July 19, 2015, 5:54 p.m., Benjamin Hindman wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/36605/
> -----------------------------------------------------------
> 
> (Updated July 19, 2015, 5:54 p.m.)
> 
> 
> Review request for mesos, Ian Downes and Timothy Chen.
> 
> 
> Bugs: MESOS-3079
>     https://issues.apache.org/jira/browse/MESOS-3079
> 
> 
> Repository: mesos
> 
> 
> Description
> -------
> 
> See summary.
> 
> 
> Diffs
> -----
> 
>   src/tests/cgroups_tests.cpp ac431beb04598d257aa98bef52a991585fe7f1ab 
>   src/tests/perf_tests.cpp 281eed0094faead67dc7f84df6407686aae88b01 
> 
> Diff: https://reviews.apache.org/r/36605/diff/
> 
> 
> Testing
> -------
> 
> make check
> 
> 
> Thanks,
> 
> Benjamin Hindman
> 
>

Reply via email to