Jenkins build is back to normal : Mesos » autotools,gcc,--verbose,GLOG_v=1 MESOS_VERBOSE=1,ubuntu:14.04,(docker||Hadoop)&&(!ubuntu-us1)&&(!ubuntu-6) #2884

See

Re: Build failed in Jenkins: Mesos » autotools,clang,--verbose --enable-libevent --enable-ssl,GLOG_v=1 MESOS_VERBOSE=1,ubuntu:14.04,(docker||Hadoop)&&(!ubuntu-us1)&&(!ubuntu-6) #2873

https://issues.apache.org/jira/browse/MESOS-6544 https://issues.apache.org/jira/browse/MESOS-6545 On Thu, Nov 3, 2016 at 4:56 PM, Benjamin Mahler wrote: > This test uses two mock executors across two agents, which means the > agents may concurrently call into the

Re: Build failed in Jenkins: Mesos » autotools,clang,--verbose --enable-libevent --enable-ssl,GLOG_v=1 MESOS_VERBOSE=1,ubuntu:14.04,(docker||Hadoop)&&(!ubuntu-us1)&&(!ubuntu-6) #2873

This test uses two mock executors across two agents, which means the agents may concurrently call into the TestContainerizer to launch the container. The TestContainerizer is not a Process and so we may concurrently modify its data structures, I suspect that the following executes concurrently and

Re: Build failed in Jenkins: Mesos » autotools,gcc,--verbose --enable-libevent --enable-ssl,GLOG_v=1 MESOS_VERBOSE=1,centos:7,(docker||Hadoop)&&(!ubuntu-us1)&&(!ubuntu-6) #2863

The logs are rotated away, can't capture them. On Wed, Nov 2, 2016 at 12:41 AM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See COMPILER=gcc,CONFIGURATION=--verbose%20--enable-libevent% >

Jenkins build is back to normal : Mesos » autotools,gcc,--verbose --enable-libevent --enable-ssl,GLOG_v=1 MESOS_VERBOSE=1,centos:7,(docker||Hadoop)&&(!ubuntu-us1)&&(!ubuntu-6) #2879

See

Jenkins build is back to normal : Mesos » cmake,gcc,--verbose --enable-libevent --enable-ssl,GLOG_v=1 MESOS_VERBOSE=1,ubuntu:14.04,(docker||Hadoop)&&(!ubuntu-us1)&&(!ubuntu-6) #2877

See

Jenkins build is back to normal : Mesos » cmake,gcc,--verbose --enable-libevent --enable-ssl,GLOG_v=1 MESOS_VERBOSE=1,centos:7,(docker||Hadoop)&&(!ubuntu-us1)&&(!ubuntu-6) #2877

See