Hi,
When compiling mesos under centos 6.5, I get numerous errors at some point,
which if I understand correctly, is at creating the mesos.jar, at the javadoc
phase:
I get the following:
http://pastebin.com/TNRERS4p
When I give mvn more JVM memory, actual errors appear (these are just two, of
./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 <
>> hansbog...@gm
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,
Hi all,
Maybe I’m missing context info on how something like a GPU as a resource should
work, but I assume that the general scenario would be that the GPU host
application would still need memory and cpu(s) co-located on the node.
In the case of,
> 4) scarceSorter include 1 agent with (gpus:1)
the whole current unix-process, which is not what
I need.
I did read about `delay(…)` but that only makes sense, if I’m correct, when the
caller is needed to wait a specific amount of time before starting another
process.
Hope someone can help.
Regards,
Hans van den Bogert
proposed solution should be.
How would your solution look in code?
Thanks in advance,
Hans van den Bogert
> On Jun 28, 2016, at 1:19 AM, Joris Van Remoortere <jo...@mesosphere.io> wrote:
>
> Hi Hans,
> If you delay, and then the lambda that you schedule is a `defer` on to
