> On Sept. 4, 2014, 5:03 p.m., Thomas Rampelberg wrote: > > :thumbsup: > > > > Is there any reason we're not running `test-containerizer` as part of the > > normal unit tests? I'd hate for something like this to happen accidentally > > again.
Yes, the reason is that the tests around the external containerizer are unfortunately broken. I am in the process of getting that fixed, hence I noticed that issue. - Till ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/25334/#review52316 ----------------------------------------------------------- On Sept. 4, 2014, 11:46 a.m., Till Toenshoff wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/25334/ > ----------------------------------------------------------- > > (Updated Sept. 4, 2014, 11:46 a.m.) > > > Review request for mesos, Benjamin Hindman, Tom Arnfeld, Thomas Rampelberg, > and Vinod Kone. > > > Bugs: MESOS-1750 > https://issues.apache.org/jira/browse/MESOS-1750 > > > Repository: mesos-git > > > Description > ------- > > Fixes defective import introduced by the flat folder hierachy of the > mesos.interface Python egg generation. > > > Diffs > ----- > > src/Makefile.am 5526189 > > Diff: https://reviews.apache.org/r/25334/diff/ > > > Testing > ------- > > make check (OSX and linux) > functional test by running build/src/examples/python/test-containerizer > > > Thanks, > > Till Toenshoff > >
