Re: Mesos 0.27.0 release update

try master branch, make check on macos 10.11.2 [ RUN ] SubcommandTest.Dispatch Subcommand 'subcommand' is not available Usage: command [OPTIONS] Available subcommands: help subcommand2 Multiple subcommands have name 'subcommand' [ OK ] SubcommandTest.Dispatch (0 ms)

Re: Mesos 0.27.0 release update

This looks new. Is it reproducible? Could you please file a JIRA for it to track properly? On Tue, Jan 26, 2016 at 6:26 PM, tommy xiao wrote: > try master branch, make check on macos 10.11.2 > > [ RUN ] SubcommandTest.Dispatch > > Subcommand 'subcommand' is not available

Re: Mesos 0.27.0 release update

I ran into an issue when tried Mesos 0.26 version and started a marathon app using URI (with maprfs path) on a mesos cluster. The issue seems to be caused by Mesos-3602 fix, and is causing issue for maprfs (mapr filesystem) when specified maprfs path as URI on marathon. The issue is that, It is

Re: Mesos 0.27.0 release update

Hi Sarjeet, I hope we fixed this in upcoming 0.27: https://issues.apache.org/jira/browse/MESOS-4304 Bernd > On Jan 25, 2016, at 7:30 PM, Sarjeet Singh wrote: > > I ran into an issue when tried Mesos 0.26 version

Re: Mesos 0.27.0 release update

We're creating a release from latest master this as soon as the remaining two blockers are resolved, current estimate should be tomorrow. Please go ahead and try out the latest master if you can. Thanks! Tim On Mon, Jan 25, 2016 at 11:53 AM, Sarjeet Singh wrote: >

Mesos 0.27.0 release update

Hi all, (Kapil, MPark and I) We're still having 3 blocker issues outstanding at this moment: MESOS-4449: SegFault on agent during executor startup (shepherd: Joris) MESOS-4441: Do not allocate non-revocable resources beyond quota guarantee. (shepherd: Joris) MESOS-4410: Introduce protobuf for

Re: Mesos 0.27.0 release update

Tests all passed in ubuntu 14.04 with kernel 3.13 and docker engine 1.9.1. On Sat, Jan 23, 2016 at 3:11 AM, Timothy Chen wrote: > Hi all, > > (Kapil, MPark and I) We're still having 3 blocker issues outstanding > at this moment: > > MESOS-4449: SegFault on agent during