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

Not yet sure what to make of this failure. There seems to be some interleaving in the logs in Jenkins, which doesn't help - has anybody seen that before? The glog logs produced during the execution of the test bodies are delayed with respect to the gtest log lines like "[ RUN ]

Re: Jenkins build is back to normal : Mesos-Windows #475

Looks like Jenkins doesn't send an email if the build machine restarts (or similar) during the build: Agent went offline during the build The Windows build didn't actually break. On Wed, Sep 7, 2016 at 2:56 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See

Jenkins build is back to normal : Mesos-Windows #475

See

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

Oof, yea I don't see a ticket for this. I'll triage and create one. On Wed, Sep 7, 2016 at 1:39 PM, Vinod Kone wrote: > segfault! is this new? > > On Tue, Sep 6, 2016 at 10:03 PM, Apache Jenkins Server < > jenk...@builds.apache.org> wrote: > > > See

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

segfault! is this new? On Tue, Sep 6, 2016 at 10:03 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See COMPILER=gcc,CONFIGURATION=--verbose,ENVIRONMENT=GLOG_v=1% >