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

Hi, >> What do folks think about removing future timeouts in tests altogether? >> Instead, we can time the whole suite differently on different CIs? > Has there been any response from the ASF Infra folks on addressing the > VM/hardware issues? Seems like it will be difficult to get good signal >

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

Has there been any response from the ASF Infra folks on addressing the VM/hardware issues? Seems like it will be difficult to get good signal from the ASF CI in the absence of some improvements on the infrastructure side. Neil On Wed, Nov 16, 2016 at 10:45 AM, Alex R wrote: >

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

Looks like VM lag again: http://pastebin.com/GZhG4fuN What do folks think about removing future timeouts in tests altogether? Instead, we can time the whole suite differently on different CIs? On 16 November 2016 at 15:30, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See