It looks like https://reviews.apache.org/r/66621/ broke the SSL
configuration:
../../../3rdparty/libprocess/src/tests/jwt_tests.cpp:26:24: fatal error:
jwt_keys.hpp: No such file or directory
On 05/18/2018 5:24 pm, Apache Jenkins Server wrote:
Branch: origin/master
The Apache Jenkins build
The SSL configurations are still failing (unrelated to most recent
commits). Other failed configuration seems to be a flaky test:
[ FAILED ] UriDiskProfileAdaptorTest.FetchFromHTTP
3: [ RUN ] UriDiskProfileAdaptorTest.FetchFromHTTP
3: I0521 19:50:59.670986 16346 process.cpp:3583] Handl
This seems weird, the failures were for a variety of reasons (maybe all
flakiness?).
On CentOS, they were both due to Docker, and both were the GCC libevent
+ SSL configurations:
Build timed out (after 300 minutes). Marking the build as failed.
Build was aborted
Error response from daemon: co
Investigated, appears to be a spurious failure. Exactly one
configuration (CentOS 7 with Autotools without libevent/OpenSSL) failed
with this:
23:44:07 [ PASSED ] 1925 tests.
23:44:07 [ FAILED ] 1 test, listed below:
23:44:07 [ FAILED ] DiskQuotaTest.SlaveRecovery
23:32:39 ../../src/
One of the two build configurations (clang on Ubuntu) compiled, ran
tests, passed, and built the distributions. However, at the end it had
exceeded 300 minutes and so failed:
Build timed out (after 300 minutes). Marking the build as failed.
The other build configuration (GCC on CentOS), comp
It looks to me that these are still building and passing tests
successfully, but the builds get marked as a failure because they time
out after 300 minutes when creating the distribution.
Perhaps we should move the `make install` step to a separate job so that
CI builds stick to compilation /
One configuration failed with a flaky test: [ FAILED ]
ExamplesTest.DynamicReservationFramework
On 03/09/2018 9:59 pm, Apache Jenkins Server wrote:
Branch: origin/1.5.x
The Apache Jenkins build system has built Mesos-Buildbot (build #5074)
Status: Still Failing
Check console output at
http
