Re: Apache Mesos Community Sync

2015-12-22 Thread Michael Park
Our last community sync was supposed to be on Dec 17, unfortunately we missed it. Sorry if anyone was looking for where it was happening. The next one would have been on Dec 31, but given that most people will likely be out for holidays I've updated the calendar to cancel it. Our next meeting is

Re: shepherd for MESOS-3909

2015-12-22 Thread Joris Van Remoortere
I will. I think Joseph can (and already has) help review this. — *Joris Van Remoortere* Mesosphere On Tue, Dec 22, 2015 at 11:02 AM, James Peach wrote: > Hi all, > > Can anyone shepherd https://issues.apache.org/jira/browse/MESOS-3909? > > Mesos modules depend on picojson, which AFAICT is not i

shepherd for MESOS-3909

2015-12-22 Thread James Peach
Hi all, Can anyone shepherd https://issues.apache.org/jira/browse/MESOS-3909? Mesos modules depend on picojson, which AFAICT is not included in any distributions. This change installs picojson.h if Mesos was built with the bundled picojson (99% of cases IMHO). Even if you bring your own piconjs

Re: How to run a single test

2015-12-22 Thread haosdent
This slide should be helpful for you. http://events.linuxfoundation.org/sites/events/files/slides/mesosconeu15_park.pdf You could switch to `Tests` chapter directly. On Wed, Dec 23, 2015 at 1:01 AM, haosdent wrote: > Hi, you could use `make -j8 check GTEST_FILTER="Your test case name"` or > `./b

Re: How to run a single test

2015-12-22 Thread haosdent
Hi, you could use `make -j8 check GTEST_FILTER="Your test case name"` or `./bin/mesos-tests.sh --gtest_filter="Your test case name"`. Test case name here looks like `LinuxFilesystemIsolatorTest.ROOT_ImageInVolumeWithRootFilesystem`. On Wed, Dec 23, 2015 at 12:54 AM, Hans van den Bogert wrote: >

How to run a single test

2015-12-22 Thread Hans van den Bogert
Hi, I’m trying to understand how the allocator/DRF works in some instances, and wanted to use some existing tests in src/test/ to play with. However changing one use case and running `make check` takes too long to iteratively develop. Is there a way to compile/run specific tests? Thanks, Ha

Re: Incompleteness of ContainerInfo.DockerInfo.DockerInfo ?

2015-12-22 Thread Viktor Sadovnikov
Thank you On Tue, Dec 22, 2015 at 5:11 AM, Adam Bordelon wrote: > Viktor, you are correct that Mesos' DockerInfo doesn't have explicit > support for the ip:hostPort:containerPort format, but you can use the > DockerInfo.parameters field to pass arbitrary parameters to the docker > CLI. > https:/