Re: [VOTE] Release Apache Mesos 1.3.0 (rc3)

2017-05-30 Thread Gastón Kleiman
On Tue, May 30, 2017 at 3:43 PM, Neil Conway wrote: > On Tue, May 30, 2017 at 2:36 PM, Vinod Kone wrote: > > Ran on ASF CI. > > > > Found following issues. > > > > Failed test: CommandExecutorCheckTest.CommandCheckDeliveredAndReconciled > >

Coverity Scan: Analysis completed for Mesos

2017-05-30 Thread scan-admin
Your request for analysis of Mesos has been completed successfully. The results are available at

Re: [VOTE] Release Apache Mesos 1.3.0 (rc3)

2017-05-30 Thread Neil Conway
On Tue, May 30, 2017 at 2:36 PM, Vinod Kone wrote: > Ran on ASF CI. > > Found following issues. > > Failed test: CommandExecutorCheckTest.CommandCheckDeliveredAndReconciled >

Re: Isolating metrics collection from master/agent slowness

2017-05-30 Thread Zhitao Li
Hi Benjamin, Thanks for the response. I agree that we should get all the 4 options start as early as we can. The reason I'm pushing for the 5) option is that we probably won't get everything fixed within 1-2 minor release cycles, and I need a way to get around the problem badly. Also, with a

Re: [VOTE] Release Apache Mesos 1.3.0 (rc3)

2017-05-30 Thread Vinod Kone
Ran on ASF CI. Found following issues. Failed test: CommandExecutorCheckTest.CommandCheckDeliveredAndReconciled

Re: Moving Mesos builds reqs from GCC 4.8.1+ to GCC 4.9.0+

2017-05-30 Thread Neil Conway
On Tue, May 30, 2017 at 12:58 PM, Michael Park wrote: > I'm all for moving to GCC 4.9+. > > I'd love to get C++14 and bump to GCC 5, but I think we should do an > investigation for "reasonable availability" before we do that. I agree, although I'd think a similar investigation

Re: Moving Mesos builds reqs from GCC 4.8.1+ to GCC 4.9.0+

2017-05-30 Thread Svante Karlsson
C++14 would be nice, btw in addition to the list above - Ubuntu 16.04 has gcc 5.4.0

Re: Moving Mesos builds reqs from GCC 4.8.1+ to GCC 4.9.0+

2017-05-30 Thread Michael Park
I'm all for moving to GCC 4.9+. I'd love to get C++14 and bump to GCC 5, but I think we should do an investigation for "reasonable availability" before we do that. Also, clang has supported C++14 / since 3.5, which is our current requirement. On Tue, May 30, 2017 at 12:50 PM, Benjamin Mahler

Re: Moving Mesos builds reqs from GCC 4.8.1+ to GCC 4.9.0+

2017-05-30 Thread Benjamin Mahler
There's a spreadsheet linked in https://issues.apache.org/jira/browse/MESOS-2604 that captures which OSes we can support based on compiler version: https://docs.google.com/spreadsheets/d/1Ji8p3p_1JqUsMxE31mJqqztHf7LDx7mGMXh253azWpU/edit#gid=0 Also, do we have already have a minimum clang version

Re: Moving Mesos builds reqs from GCC 4.8.1+ to GCC 4.9.0+

2017-05-30 Thread Neil Conway
It seems that if we moved to GCC 5, we'd also be able to move to C++14 (https://gcc.gnu.org/projects/cxx-status.html#cxx14). CentOS 6 users will need to install devtoolset anyway (which makes it easy to get GCC 5 or 6), so I wonder if skipping directly to requiring GCC 5 would be feasible? Neil

Moving Mesos builds reqs from GCC 4.8.1+ to GCC 4.9.0+

2017-05-30 Thread Jacob Janco
Along with various additions and optimizations, support for would be nice to have. Thoughts on this?

Mesos on Windows needs your help

2017-05-30 Thread Li Li
With the joint effort from Mesosphere and Microsoft, the windows build performance *should* be about equal with Posix/Linux now, ~76% tests are enabled on the ported windows components, and Mesos container/docker container tasks are launched successfully e2e. We will start helping Mesos windows