> On Sept. 6, 2016, 9:59 a.m., Guangya Liu wrote: > > src/tests/hierarchical_allocator_tests.cpp, line 2594 > > <https://reviews.apache.org/r/51028/diff/2/?file=1476333#file1476333line2594> > > > > Seems we should also `Clock::settle();` here, otherwise, this test may > > be failed as r/51027
Since there is an `AWAIT_READY(allocation)` beforehand for the previous 2 calls to the allocator, I believe we should be OK here. - Jacob ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/51028/#review147809 ----------------------------------------------------------- On Aug. 23, 2016, 8:47 a.m., Jacob Janco wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/51028/ > ----------------------------------------------------------- > > (Updated Aug. 23, 2016, 8:47 a.m.) > > > Review request for mesos and Jiang Yan Xu. > > > Bugs: MESOS-3157 > https://issues.apache.org/jira/browse/MESOS-3157 > > > Repository: mesos > > > Description > ------- > > - Per MESOS-3157, if cluster events with the possibility > of triggering an allocation occur rapidly and test > assertions depend on gleaning information from assumed > order, it is likely they will fail due to lack of parity > between event and actual allocation. Settle the clock > between these events in tests sensitive to this to ensure > expected allocations occur. > > > Diffs > ----- > > src/tests/hierarchical_allocator_tests.cpp > cbed333f497016fe2811f755028796012b41db77 > > Diff: https://reviews.apache.org/r/51028/diff/ > > > Testing > ------- > > make check > > > Thanks, > > Jacob Janco > >
