> On Jan. 23, 2015, 1:27 a.m., Niklas Nielsen wrote: > > src/tests/master_allocator_tests.cpp, line 89 > > <https://reviews.apache.org/r/29927/diff/2/?file=826946#file826946line89> > > > > Can we to guard this so you capture dispatches to a 'stopped' allocator > > upfront?
I'll add a `CHECK` macro. - Alexander ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/29927/#review69318 ----------------------------------------------------------- On Jan. 20, 2015, 6:10 p.m., Alexander Rukletsov wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/29927/ > ----------------------------------------------------------- > > (Updated Jan. 20, 2015, 6:10 p.m.) > > > Review request for mesos, Bernd Mathiske and Niklas Nielsen. > > > Bugs: MESOS-2213 > https://issues.apache.org/jira/browse/MESOS-2213 > > > Repository: mesos-git > > > Description > ------- > > Several tests have been reported flaky if allocation is not ceased explicitly > (see MESOS-1677). To stop allocation, an allocator instance should be > destroyed. To facilitate this, store a pointer to a MockAllocator instance in > the MasterAllocatorTest fixture and let a test case destroy it. > > > Diffs > ----- > > src/tests/master_allocator_tests.cpp 2430622 > > Diff: https://reviews.apache.org/r/29927/diff/ > > > Testing > ------- > > make check (Ubuntu, OS X) > > > Thanks, > > Alexander Rukletsov > >
