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: conflict: unable to delete e804ecae6ec0
(cannot be forced) - image is being used by running container
4fa36117b345
Error response from daemon: conflict: unable to delete 4ecb5a128921
(cannot be forced) - image is being used by running container
365f857ab9c5
Finished: FAILURE
On Ubuntu, the first failure was just after the test:
[ RUN ] SlaveTest.AgentFailoverTerminatesHTTPExecutorWithNoTask
The second and third failures had a stack trace after the test:
[ RUN ] SlaveRecoveryTest/0.PingTimeoutDuringRecovery
And all three of those failures were with Clang, but the other
configurations succeeded.
Any ideas?
On 06/08/2018 1:19 am, Apache Jenkins Server wrote:
Branch: origin/master
The Apache Jenkins build system has built Mesos-Buildbot (build #5358)
Status: Still Failing
Check console output at
https://builds.apache.org/job/Mesos-Buildbot/5358/ to view the
results.
