Re: Build failed in Jenkins: Mesos » Mesos-Tidybot » -DENABLE_LIBEVENT=ON -DENABLE_SSL=ON,ubuntu #168

ybot/CMAKE_ARGS=-DENABLE_LIBEVENT=ON%20-DENABLE_SSL=ON,label_exp=ubuntu/168/display/redirect?page=changes > > > > Changes: > > [Benjamin Mahler] [mesos-tidy] Fix broken Dockerfile due to llvm repo move. > > > -- > [...truncated 571.48 KB.

Re: Build failed in Jenkins: Mesos » Mesos-Reviewbot #30672

+dleamy I cleaned up dleamy's reviews that had bad dependencies, I believe these failures should stop now. On Wed, Mar 13, 2024 at 6:14 PM Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See < > https://ci-builds.apache.org/job/Mesos/job/Mesos-Reviewbot/30672/display/redirect > > >

Re: Build failed in Jenkins: Mesos » Mesos-Tidybot » -DENABLE_LIBEVENT=OFF -DENABLE_SSL=OFF,ubuntu #143

Fixed the image here: https://github.com/apache/mesos/pull/516 Pinged michael to get access to the dockerhub repository so that I can upload a new one. I can then update our readme accordingly. On Tue, Feb 20, 2024 at 2:24 PM Benjamin Mahler wrote: > +cf-natali > > Looks like we need

Re: Build failed in Jenkins: Mesos » Mesos-Tidybot » -DENABLE_LIBEVENT=OFF -DENABLE_SSL=OFF,ubuntu #143

harles, are you able to build and upload a new tidy image? On Mon, Feb 19, 2024 at 11:25 PM Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See < > https://ci-builds.apache.org/job/Mesos/job/Mesos-Tidybot/CMAKE_ARGS=-DENABLE_LIBEVENT=OFF%20-DENABLE_SSL=OFF,label_exp=ubunt

Re: Build failed in Jenkins: Mesos » Mesos-Tidybot » -DENABLE_LIBEVENT=ON -DENABLE_SSL=ON,ubuntu #119

9/display/redirect?page=changes > > > > Changes: > > [Benjamin Mahler] Reduced the number of jemalloc arenas. > > [Benjamin Mahler] Added ECN configuration copying from the host to the > container. > > [Benjamin Ma

Re: Branch: origin/master Mesos-Buildbot - Build # 6937 - Failure

Known failure: https://issues.apache.org/jira/browse/MESOS-8983 On Fri, Mar 6, 2020 at 6:25 PM Apache Jenkins Server < jenk...@builds.apache.org> wrote: > Branch: origin/master > > The Apache Jenkins build system has built Mesos-Buildbot (build #6937) > > Status: Failure > > Check console

Re: Branch: origin/master Mesos-Buildbot - Build # 6674 - Still Failing

https://issues.apache.org/jira/browse/MESOS-9939 On Tue, Aug 13, 2019 at 5:07 PM Apache Jenkins Server < jenk...@builds.apache.org> wrote: > Branch: origin/master > > The Apache Jenkins build system has built Mesos-Buildbot (build #6674) > > Status: Still Failing > > Check console output at

Re: Branch: origin/master Mesos-Buildbot - Build # 6547 - Still Failing

+Chun-Hung Hsiao On Fri, Jun 21, 2019 at 6:43 PM Apache Jenkins Server < jenk...@builds.apache.org> wrote: > Branch: origin/master > > The Apache Jenkins build system has built Mesos-Buildbot (build #6547) > > Status: Still Failing > > Check console output at

Re: Branch: origin/master Mesos-Buildbot - Build # 6546 - Failure

+Chun-Hung Hsiao On Fri, Jun 21, 2019 at 4:56 PM Apache Jenkins Server < jenk...@builds.apache.org> wrote: > Branch: origin/master > > The Apache Jenkins build system has built Mesos-Buildbot (build #6546) > > Status: Failure > > Check console output at

Re: Branch: origin/master Mesos-Buildbot - Build # 6536 - Still Failing

+chun On Mon, Jun 17, 2019 at 9:10 PM Apache Jenkins Server < jenk...@builds.apache.org> wrote: > Branch: origin/master > > The Apache Jenkins build system has built Mesos-Buildbot (build #6536) > > Status: Still Failing > > Check console output at

Re: Build failed in Jenkins: Mesos-Tidybot » -DENABLE_LIBEVENT=ON -DENABLE_SSL=ON,(docker||Hadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2) #2091

+Andrei Sekretenko Looks like there's a tidy check for capturing this in a callback without a 'defer'. While it's technically safe in this case, it's brittle and can easily become unsafe if the future gets satisfied not by the master actor. While ideally we send the framework error message

Re: Branch: origin/1.7.x Mesos-Buildbot - Build # 5595 - Still Failing

Looks like a docker error? On Wed, Aug 15, 2018 at 6:22 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > Branch: origin/1.7.x > > The Apache Jenkins build system has built Mesos-Buildbot (build #5595) > > Status: Still Failing > > Check console output at

Re: Branch: origin/master Mesos-Buildbot - Build # 5294 - Still Failing

Just seeing now that this ticket was filed, my email filter was putting all builds@ emails into a folder even if sent to me. On Thu, May 17, 2018 at 1:15 AM, Alex R wrote: > This looks new: https://issues.apache.org/jira/browse/MESOS-8930 > Ben, Gilbert, can you please have a look? > > On 17

Re: Branch: origin/master Mesos-Buildbot - Build # 5511 - Still Failing

https://reviews.apache.org/r/68073/ On Thu, Jul 26, 2018 at 4:01 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > Branch: origin/master > > The Apache Jenkins build system has built Mesos-Buildbot (build #5511) > > Status: Still Failing > > Check console output at

Re: Branch: origin/master Mesos-Buildbot - Build # 5509 - Still Failing

Pushed a fix. On Thu, Jul 26, 2018 at 12:13 PM, Benjamin Mahler wrote: > Another distcheck rapidjson issue: > > 17:39:21 ERROR: files left in build directory after distclean: > 17:39:21 ./3rdparty/._rapidjson-1.1.0 > 17:39:21 make[1]: *** [distcleancheck] Error 1 > 17:39:2

Re: Branch: origin/master Mesos-Buildbot - Build # 5509 - Still Failing

Another distcheck rapidjson issue: 17:39:21 ERROR: files left in build directory after distclean: 17:39:21 ./3rdparty/._rapidjson-1.1.0 17:39:21 make[1]: *** [distcleancheck] Error 1 17:39:21 make[1]: Leaving directory `/tmp/SRC/build/mesos-1.7.0/_build' 17:39:21 make: *** [distcheck] Error 1

Re: Branch: origin/master Mesos-Buildbot - Build # 5505 - Still Failing

Rapidjson fix was pushed already but not picked up yet by this run. On Wed, Jul 25, 2018 at 5:11 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > Branch: origin/master > > The Apache Jenkins build system has built Mesos-Buildbot (build #5505) > > Status: Still Failing > > Check

Fwd: Branch: origin/master Mesos-Buildbot - Build # 5504 - Still Failing

Pushing a fix shortly. -- Forwarded message -- From: Apache Jenkins Server Date: Wed, Jul 25, 2018 at 3:06 PM Subject: Branch: origin/master Mesos-Buildbot - Build # 5504 - Still Failing To: builds@mesos.apache.org Branch: origin/master The Apache Jenkins build system has

Re: Branch: origin/master Mesos-Buildbot - Build # 4984 - Still Failing

Hm.. *19:08:27* docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?.*19:08:27* See 'docker run --help'.*19:08:27* Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?*19:08:27* "docker rmi" requires

Re: Build failed in Jenkins: Mesos-Buildbot » cmake,clang,--verbose --disable-libtool-wrappers,GLOG_v=1 MESOS_VERBOSE=1,ubuntu:14.04,(ubuntu)&&(!ubuntu-us1)&&(!ubuntu-eu2)&&(!qnode3)&&(!H23) #4458

I believe this is the getenv during setenv crash that hasn't been fixed yet. On Wed, Nov 15, 2017 at 12:24 AM Alex R wrote: > +Ben, FYI > > On 14 November 2017 at 23:24, Apache Jenkins Server < > jenk...@builds.apache.org> wrote: > >> See < >>

Re: Build failed in Jenkins: Mesos-Buildbot » autotools,clang,--verbose --disable-libtool-wrappers --enable-libevent --enable-ssl,GLOG_v=1 MESOS_VERBOSE=1,ubuntu:14.04,(ubuntu)&&(!ubuntu-us1)&&(!ubunt

Filed: https://issues.apache.org/jira/browse/MESOS-8152 On Mon, Oct 30, 2017 at 10:59 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See autotools,COMPILER=clang,CONFIGURATION=--verbose%20-- >

Re: Build failed in Jenkins: Mesos-Reviewbot #19874

+alexr Looks like the destruction order here is wrong and the mock gets called after being destructed? Alex I seem to remember you mentioning something like this? Is this a known issue? On Sun, Oct 22, 2017 at 2:49 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See

Re: Build failed in Jenkins: Mesos-Buildbot » autotools,clang,--verbose --disable-libtool-wrappers --enable-libevent --enable-ssl,GLOG_v=1 MESOS_VERBOSE=1,ubuntu:14.04,(ubuntu)&&(!ubuntu-us1)&&(!ubunt

Captured by https://issues.apache.org/jira/browse/MESOS-7972 Posted a fix here: https://reviews.apache.org/r/63391/ On Thu, Oct 26, 2017 at 4:26 AM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See

Re: Build failed in Jenkins: Mesos-Buildbot » autotools,gcc,--verbose --disable-libtool-wrappers --enable-libevent --enable-ssl,GLOG_v=1 MESOS_VERBOSE=1,ubuntu:14.04,(ubuntu)&&(!ubuntu-us1)&&(!ubuntu-

Updated https://issues.apache.org/jira/browse/MESOS-1553. On Wed, Oct 25, 2017 at 9:49 AM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See autotools,COMPILER=gcc,CONFIGURATION=--verbose%20-- >

Re: Build failed in Jenkins: Mesos-Buildbot » cmake,gcc,--verbose --disable-libtool-wrappers,GLOG_v=1 MESOS_VERBOSE=1,ubuntu:14.04,(ubuntu)&&(!ubuntu-us1)&&(!ubuntu-eu2)&&(!qnode3)&&(!H23) #4359

This looks like a timeout: 3: I1024 04:12:32.741120 17193 replica.cpp:540] Replica received write request for position 1 from __req_res__(1523)@172.17.0.2:51271 3: I1024 04:12:32.741189 17201 replica.cpp:540] Replica received write request for position 1 from __req_res__(1524)@172.17.0.2:51271 3:

Re: Build failed in Jenkins: Mesos-Buildbot » cmake,gcc,--verbose --disable-libtool-wrappers,GLOG_v=1 MESOS_VERBOSE=1,centos:7,(ubuntu)&&(!ubuntu-us1)&&(!ubuntu-eu2)&&(!qnode3)&&(!H23) #4359

+gaston, you're assigned to this ticket? Are you still planning to look into this? https://issues.apache.org/jira/browse/MESOS-7742 On Mon, Oct 23, 2017 at 9:13 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See

Re: Build failed in Jenkins: Mesos-Buildbot » autotools,clang,--verbose --disable-libtool-wrappers,GLOG_v=1 MESOS_VERBOSE=1,ubuntu:14.04,(ubuntu)&&(!ubuntu-us1)&&(!ubuntu-eu2)&&(!qnode3)&&(!H23) #4355

+jie, gaston, benjamin, gilbert Looks like there wasn't a ticket for this, created one: https://issues.apache.org/jira/browse/MESOS-8124 Can one of you look into this? On Sun, Oct 22, 2017 at 7:04 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See

Re: Build failed in Jenkins: Mesos-Buildbot » cmake,gcc,--verbose --disable-libtool-wrappers --enable-libevent --enable-ssl,GLOG_v=1 MESOS_VERBOSE=1,ubuntu:14.04,(ubuntu)&&(!ubuntu-us1)&&(!ubuntu-eu2)

Chatted with greg, looks like Ilya's suggestion in https://issues.apache.org/jira/browse/MESOS-6985 is a good fix. Ilya, would you be able to work on the fix? On Sun, Oct 22, 2017 at 9:58 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See

Re: Build failed in Jenkins: Mesos-Buildbot » autotools,gcc,--verbose --disable-libtool-wrappers,GLOG_v=1 MESOS_VERBOSE=1,centos:7,(ubuntu)&&(!ubuntu-us1)&&(!ubuntu-eu2)&&(!qnode3)&&(!H23) #4357

Is anyone digging into these? I see no activity on https://issues.apache.org/jira/browse/MESOS-7440. On Sun, Oct 22, 2017 at 10:40 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See

Re: Build failed in Jenkins: Mesos-Buildbot » autotools,clang,--verbose --disable-libtool-wrappers,GLOG_v=1 MESOS_VERBOSE=1,ubuntu:14.04,(ubuntu)&&(!ubuntu-us1)&&(!ubuntu-eu2)&&(!qnode3)&&(!H23) #4358

Posted a fix here: https://reviews.apache.org/r/63224/ On Mon, Oct 23, 2017 at 1:16 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See autotools,COMPILER=clang,CONFIGURATION=--verbose%20-- >

Re: Build failed in Jenkins: Mesos-Buildbot » cmake,clang,--verbose --enable-libevent --enable-ssl,GLOG_v=1 MESOS_VERBOSE=1,ubuntu:14.04,(docker||Hadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2) #3218

+Kevin Is this a known issue? [ FAILED ] IOSwitchboardTest.RecoverThenKillSwitchboardContainerDestroyed On Fri, Feb 3, 2017 at 6:41 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See

Re: Build failed in Jenkins: Mesos-Reviewbot #16979

+neil Is this test flaky? [ FAILED ] ReconciliationTest.UnknownTaskPartitionAware It also appears that other reconciliation tests failed in other runs of the reviewbot. On Sat, Feb 4, 2017 at 12:27 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See

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

+neil Is this test flaky? I wasn't able to grab the logs since jenkins appears to be non-responsive at the moment. [ FAILED ] RegistrarTest.PruneUnreachable On Sat, Feb 4, 2017 at 3:03 AM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See

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

It looks like the builds running on 'ubuntu-eu2' fail from OOMing, but the ones that run on 'H2' work. https://builds.apache.org/computer/ubuntu-eu2/ https://builds.apache.org/computer/H1/ Vinod does this have to do with our label update? Unfortunately I can't seem to find any information on how

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

https://issues.apache.org/jira/browse/MESOS-6544 https://issues.apache.org/jira/browse/MESOS-6545 On Thu, Nov 3, 2016 at 4:56 PM, Benjamin Mahler <bmah...@apache.org> wrote: > This test uses two mock executors across two agents, which means the > agents may concu

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

This test uses two mock executors across two agents, which means the agents may concurrently call into the TestContainerizer to launch the container. The TestContainerizer is not a Process and so we may concurrently modify its data structures, I suspect that the following executes concurrently and

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

The logs are rotated away, can't capture them. On Wed, Nov 2, 2016 at 12:41 AM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See COMPILER=gcc,CONFIGURATION=--verbose%20--enable-libevent% >

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

Should be fixed now. On Tue, Jul 5, 2016 at 11:23 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See < >

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

Should be fixed. On Sat, Jul 2, 2016 at 5:42 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See < >

Re: Build failed in Jenkins: Mesos » cmake,gcc,--verbose --enable-libevent --enable-ssl,GLOG_v=1 MESOS_VERBOSE=1,centos:7,(docker||Hadoop)&&(!ubuntu-us1) #2306

+Kevin On Fri, Jun 17, 2016 at 12:29 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See < >

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

Thanks for fixing! On Tue, Mar 29, 2016 at 11:36 AM, Joseph Wu <jos...@mesosphere.io> wrote: > Tracked here: https://issues.apache.org/jira/browse/MESOS-4961 > > On Tue, Mar 29, 2016 at 11:22 AM, Benjamin Mahler <bmah...@apache.org> > wrote: > > > +joseph > &g

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

Joris, Vinod, has a regression been introduced in the SSL tests? On Tue, Mar 29, 2016 at 11:21 AM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See < >

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

+joseph On Mon, Mar 28, 2016 at 11:32 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See < >

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

Hey Tim, are you planning to work on this? Or should we re-assign it? On Mon, Jan 25, 2016 at 8:54 AM, Greg Mann wrote: > We have a ticket tracking this failure here: > https://issues.apache.org/jira/browse/MESOS-1802 > > On Mon, Jan 25, 2016 at 7:32 AM, Apache Jenkins

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

It will be fixed soon. On Tue, Jan 19, 2016 at 4:34 PM, Greg Mann wrote: > Looks like it could be caused by the same issue as > https://issues.apache.org/jira/browse/MESOS-4409 > > On Tue, Jan 19, 2016 at 4:07 PM, Vinod Kone wrote: > > > Is this being

Re: Build failed in Jenkins: mesos-reviewbot #10623

Logging the body of the 500 (or other errors) might shed some light, instead of just the status: https://github.com/apache/mesos/commit/3b4d0d1eaf2f0277b45a182c33a71c321db2cf8f On Wed, Jan 6, 2016 at 4:38 PM, Vinod Kone wrote: > aha. i missed the "internal server error"

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

+vinod Hm.. we use the '--rm' flag when invoking 'docker run' so I'm not sure why the container isn't removed by the time we invoke 'docker rmi' upon exiting our script.. any ideas? On Tue, Jan 5, 2016 at 6:10 AM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See < >

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

Sorry about that. Reverted my change to add the xml reports given make distclean doesn't pick them up. I'll file a ticket for getting the reporting into jenkins. On Tue, Dec 29, 2015 at 2:24 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See < >

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

Filed: https://issues.apache.org/jira/browse/MESOS-4257 On Mon, Dec 21, 2015 at 2:21 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See < >

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

Will do On Saturday, December 12, 2015, Michael Park wrote: > Looks like the tests are hanging at various places locally on my OS X box > it hangs on *FetcherCacheHttpTest.HttpCachedConcurrent*. Could you take a > look? > > On Sat, Dec 12, 2015 at 1:51 AM Apache Jenkins Server

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

I pushed a fix for the deadlock issue in HttpTest.Endpoints. There appears to also be issues with ProcessTest.Http1 and ProcessTest.Http2. I'll look into those as well. On Sat, Dec 12, 2015 at 8:40 AM, Benjamin Mahler <benjamin.mah...@gmail.com> wrote: > Will do > > > On Sat

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

Fix for ProcessTest.Http1: https://reviews.apache.org/r/41318/ Some Subprocess test cleanups that I noticed were needed when I fixed the fd leak: https://reviews.apache.org/r/41320/ On Sat, Dec 12, 2015 at 2:33 PM, Benjamin Mahler <benjamin.mah...@gmail.com> wrote: > T

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

Fixed, sorry about that! On Wed, Dec 9, 2015 at 5:55 PM, Joseph Wu wrote: > Filed a JIRA: > https://issues.apache.org/jira/browse/MESOS-4109 > > On Wed, Dec 9, 2015 at 5:44 PM, Apache Jenkins Server < > jenk...@builds.apache.org> wrote: > > > See < > > >

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

https://issues.apache.org/jira/browse/MESOS-4024 On Wed, Dec 9, 2015 at 1:32 AM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See < > https://builds.apache.org/job/Mesos/COMPILER=gcc,CONFIGURATION=--verbose,OS=centos%3A7,label_exp=docker%7C%7CHadoop/1336/changes > > > > Changes: >

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

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: > >

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

https://issues.apache.org/jira/browse/MESOS-4059 Sorry Joseph on my last email I didn't see your ticket. Would be great to reply to all build failures for a particular test because it makes it clear when a build failure is being handled. On Thu, Dec 3, 2015 at 12:10 PM, Apache Jenkins Server <

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

Michael can you please triage this test? On Thu, Dec 3, 2015 at 7:31 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See < >

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

Got it. Who shepherded it? On Thu, Dec 3, 2015 at 7:38 PM, Michael Park <mp...@mesosphere.io> wrote: > +Greg since he's the author, he might have a better idea > > On Thu, Dec 3, 2015, 10:36 PM Benjamin Mahler <benjamin.mah...@gmail.com> > wrote: > >> Michae

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

Thank you sir! On Thu, Dec 3, 2015 at 7:45 PM, Michael Park <mp...@mesosphere.io> wrote: > Yep, I'll look into it once I get back to a computer. > > On Thu, Dec 3, 2015, 10:44 PM Benjamin Mahler <benjamin.mah...@gmail.com> > wrote: > >> Michael, this looks li

Re: Build failed in Jenkins: mesos-reviewbot #9787

Hey Vinod / Jie, It appears that these recent failures are from the review here https://reviews.apache.org/r/40418/. It looks like because verify_reviews.py hits a "500 Internal Server Error" it barfs out and emails the list. Unfortunately, this ends up being a bit misleading in this case because

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

Wondering if this is a one-off due to system issues. > RST could be caused by system memory pressure. > > -Jojy > > On Oct 13, 2015, at 1:24 PM, Benjamin Mahler <benjamin.mah...@gmail.com> > wrote: > > +tim, jojy > > Could you guys triage this test failure? > > On

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

+anand Looks like the ExamplesTest.EventCallFramework was running forever here. On Tue, Oct 13, 2015 at 5:18 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See < >

Re: Build failed in Jenkins: Mesos » gcc,--verbose --enable-libevent --enable-ssl,centos:7,docker||Hadoop #890

Fixed in: https://issues.apache.org/jira/browse/MESOS-3577 On Sat, Oct 3, 2015 at 1:31 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See < >

Re: Build failed in Jenkins: Mesos » gcc,--verbose --enable-libevent --enable-ssl,centos:7,docker||Hadoop #755

+bernd Re-opened https://issues.apache.org/jira/browse/MESOS-2858 On Mon, Aug 31, 2015 at 6:33 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See < >

Re: Build failed in Jenkins: mesos-reviewbot #7547

Hm.. https://reviews.apache.org/r/37113/ was discarded 5 hours ago, is reviewbot not ignoring discarded reviews? On Thu, Aug 6, 2015 at 7:48 PM, Benjamin Mahler benjamin.mah...@gmail.com wrote: 403 forbidden looks like more of an auth issue.. I wonder if there is a bad review url

Re: Build failed in Jenkins: mesos-reviewbot #7547

403 forbidden looks like more of an auth issue.. I wonder if there is a bad review url that reviewbot is picking up. On Thu, Aug 6, 2015 at 6:27 PM, Michael Park mcyp...@gmail.com wrote: Mm... Still failing, maybe it wasn't the git mirror issue? On Thu, Aug 6, 2015, 5:46 PM Michael Park

Re: Build failed in Jenkins: mesos-reviewbot #7415

Pushed a fix, looks like the namespace clause was missed. On Thu, Jul 30, 2015 at 5:12 PM, Apache Jenkins Server jenk...@builds.apache.org wrote: See https://builds.apache.org/job/mesos-reviewbot/7415/ -- [URLTrigger] A change within the response URL

Re: Build failed in Jenkins: Mesos » clang,docker||Hadoop,ubuntu:14.10 #589

Should be fixed, sorry about that. On Tue, Jul 28, 2015 at 2:03 PM, Apache Jenkins Server jenk...@builds.apache.org wrote: See https://builds.apache.org/job/Mesos/COMPILER=clang,LABEL=docker%7C%7CHadoop,OS=ubuntu%3A14.10/589/changes Changes: [benjamin.mahler] Updated Framework struct