Build failed in Jenkins: mesos-reviewbot #10079

See -- [...truncated 161719 lines...] [ RUN ] ContentType/SchedulerTest.Request/0 I1208 11:02:42.708636 30294 leveldb.cpp:174] Opened db in 117.309094ms I1208 11:02:42.759570 30294 leveldb.cpp:181]

Jenkins build is back to normal : Mesos » gcc,--verbose,ubuntu:14.04,docker||Hadoop #1332

See

Jenkins build is back to normal : Mesos » clang,--verbose --enable-libevent --enable-ssl,ubuntu:14.04,docker||Hadoop #1334

See

Jenkins build is back to normal : Mesos » clang,--verbose,ubuntu:14.04,docker||Hadoop #1334

See

Re: Build failed in Jenkins: Mesos » clang,--verbose,ubuntu:14.04,docker||Hadoop #1333

Hm.. the following looks like a bug in the git plugin: stderr: fatal: reference is not a tree: 8833974195e76e6e7cd8377fb511aa 2f96e409e6 I suspect this might be related to the fact that we do a shallow clone, and there seems to be a double fetch in the above output. If the SHA is obtained after

Build failed in Jenkins: Mesos » gcc,--verbose --enable-libevent --enable-ssl,ubuntu:14.04,docker||Hadoop #1334

See Changes: [benjamin.mahler] Fixed indentation in Master::initialize. --

Jenkins build is back to normal : Mesos » gcc,--verbose,ubuntu:14.04,docker||Hadoop #1334

See

Jenkins build is back to normal : Mesos » gcc,--verbose --enable-libevent --enable-ssl,ubuntu:14.04,docker||Hadoop #1335

See

Jenkins build is back to normal : mesos-reviewbot #10092

See

Build failed in Jenkins: mesos-reviewbot #10091

See -- [...truncated 8022 lines...] == real16m59.611s user92m18.841s sys 6m53.517s + chmod -R +w 3rdparty aclocal.m4 ar-lib autom4te.cache bin

Build failed in Jenkins: Mesos » gcc,--verbose,centos:7,docker||Hadoop #1335

See Changes: [mpark] Fixed flakiness in `ReservationTest.ACLMultipleOperations`. [mpark] Shortened `allocation_interval` from 50ms to 5ms in `ReservationTest`s

Build failed in Jenkins: mesos-reviewbot #10087

See Changes: [yujie.jay] Fixed hyphen usage in comments. [yujie.jay] Fixed punctuation usage in some error messages. -- [...truncated 161754 lines...] [ RUN ]

Jenkins build is back to normal : Mesos » gcc,--verbose --enable-libevent --enable-ssl,ubuntu:14.04,docker||Hadoop #1332

See

Jenkins build is back to normal : Mesos » gcc,--verbose,centos:7,docker||Hadoop #1332

See

Build failed in Jenkins: Mesos » gcc,--verbose --enable-libevent --enable-ssl,ubuntu:14.04,docker||Hadoop #1331

See -- [...truncated 149982 lines...] I1208 21:13:32.888731 31805 gc.cpp:54] Scheduling

Build failed in Jenkins: Mesos » gcc,--verbose,centos:7,docker||Hadoop #1331

See -- [...truncated 150766 lines...] I1208 21:29:59.189986 31385 gc.cpp:54] Scheduling

Re: Build failed in Jenkins: Mesos » gcc,--verbose --enable-libevent --enable-ssl,ubuntu:14.04,docker||Hadoop #1331

Thanks! We should remove the "health" code related to this, was never finished or used. On Tue, Dec 8, 2015 at 1:19 PM, Neil Conway wrote: > This build failure is due to a broken test > (HealthTest.ObserveEndpoint), and has already been fixed in master: > >

Build failed in Jenkins: Mesos » clang,--verbose --enable-libevent --enable-ssl,ubuntu:14.04,docker||Hadoop #1331

See Changes: [yujie.jay] Fixed hyphen usage in comments. [yujie.jay] Fixed punctuation usage in some error messages.