Re: Programmatically retrieve stdout/stderr from a node

Also I believe the CLI work that Haris / Kevin have been doing would make this easy to do via the Mesos CLI (it's not integrated into the project yet). On Wed, Aug 10, 2016 at 9:57 AM, Erik Weathers wrote: > Just for completeness and to provide an alternative, you can

Re: [VOTE] Release Apache Mesos 1.0.1 (rc1)

+1 (binding) You can find the rpm/deb packages here: http://open.mesosphere.com/downloads/mesos-rc/#apache-mesos-1.0.1-rc1 The following docker tags (built off of ubuntu 14.04) are also available: mesosphere/mesos:1.0.1-rc1 mesosphere/mesos-master:1.0.1-rc1

Re: [VOTE] Release Apache Mesos 1.0.1 (rc1)

+1 (binding) make check on Mac OS 10.11.6 with apple clang-703.0.31. DockerFetcherPluginTest.INTERNET_CURL_FetchImage is flaky (MESOS-4570), but this does not seem to be a regression or a blocker. On Fri, Aug 12, 2016 at 10:30 PM, Radoslaw Gruchalski wrote: > I am trying

Re: [VOTE] Release Apache Mesos 1.0.1 (rc1)

I am trying to build Mesos 1.0.1 for Centos 7 in a Docker container but I'm hitting this: https://issues.apache.org/jira/browse/MESOS-5925. Kind regards, Radek Gruchalski ra...@gruchalski.com +4917685656526 *Confidentiality:* This communication is intended for the above-named person and may be

Re: [VOTE] Release Apache Mesos 1.0.1 (rc1)

Whoops! Sorry y'all, my wires got crossed :) I ran these tests on Ubuntu 14.04. G On Fri, Aug 12, 2016 at 12:50 PM, Greg Mann wrote: > +1 (non-binding): > > * Ran "sudo make distcheck" on CentOS 7 with libevent and SSL enabled. All > tests passed. > * Used "test-upgrade.py"

Re: [VOTE] Release Apache Mesos 1.0.1 (rc1)

+1 (non-binding): * Ran "sudo make distcheck" on CentOS 7 with libevent and SSL enabled. All tests passed. * Used "test-upgrade.py" to test upgrades from 0.28.2 -> 1.0.1 and 1.0.0 -> 1.0.1; both were successful. Cheers, Greg On Wed, Aug 10, 2016 at 5:32 PM, Vinod Kone

答复: Deactivationg framework unexpectly

Hi Anindya, The problem occurred again. The following is the log of the scheduler driver log at Chronos side: I0812 08:15:43.90271296 sched.cpp:1937] Asked to abort the driver I0812 08:15:43.90276396 sched.cpp:981] Scheduler::statusUpdate took 1.436378441secs I0812 08:15:43.902788