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

Oops, missed that. I'll fix shortly... On Mon, Oct 29, 2018 at 3:22 PM Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See < >

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

These warnings should be fixed now. On Mon, Oct 29, 2018 at 12:28 PM Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See < >

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

Alex, Did we decide to disable flaky tests that have a JIRA? This build, for example, failed due to: https://issues.apache.org/jira/browse/MESOS-5804 On Thu, Feb 8, 2018 at 11:50 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > Branch: origin/master > > The Apache Jenkins build

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

Ah, my bad. `string(APPEND ...)` was added in CMake 3.4. I'll undo part of one of these changes. On Mon, May 15, 2017 at 10:42 AM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See

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

Just pushed a fix for the immediate problem (the resource_provider.proto sources weren't being generated at all). There's another problem which Benjamin pointed out in https://issues.apache.org/jira/browse/MESOS-7470 On Mon, May 8, 2017 at 11:06 AM, Apache Jenkins Server <

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

Looks like the build's stdout/stderr got a bit out of sync. The build finished: [--] Global test environment tear-down [==] 1457 tests from 160 test cases ran. (214575 ms total) [ PASSED ] 1456 tests. [ FAILED ] 1 test, listed below: [ FAILED ] MasterTest.KillTask Digging

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

Interesting. Looks like the value of `$USER` is not set in the docker builds. With the way CMake does it's input substitution, when $USER is blank, the define gets commented out. On Wed, Mar 1, 2017 at 4:08 PM, Apache Jenkins Server wrote: > See >

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

This is tracking issue: https://issues.apache.org/jira/browse/MESOS-6135 On Fri, Feb 17, 2017 at 3:23 PM, Vinod Kone wrote: > joseph? > > On Fri, Feb 17, 2017 at 1:24 PM, Apache Jenkins Server < > jenk...@builds.apache.org> wrote: > > > See

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

My mistake. Pushed the fix. On Thu, Feb 16, 2017 at 7:21 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See autotools,COMPILER=clang,CONFIGURATION=--verbose%20-- > enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1% >

Re: Build failed in Jenkins: Mesos-Windows #1221

Sorry for the spam. I forgot to disable the build last night, after talking with some of the ASF Infra folks. Disabled for now while we get this node cleared up. On Fri, Jan 27, 2017 at 10:29 AM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See

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

Yup, this matches. (HTTPTest is parameterized to run both HTTP and HTTPS.) On Wed, Jan 25, 2017 at 1:55 PM, Michael Park wrote: > This looks like it may be https://issues.apache.org/ > jira/browse/MESOS-6938...? > @Greg​: Could you confirm? >

Re: Build failed in Jenkins: Mesos-Buildbot-Windows #1124

I've opened an INFRA ticket, as the machine is apparently out of space. https://issues.apache.org/jira/browse/INFRA-13378 For now, to avoid spamming the mailing list even more, I'll disable this build. On Mon, Jan 23, 2017 at 3:07 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: >

Re: Build failed in Jenkins: Mesos-Buildbot-Windows #1119

We may have to hunt down what is causing this filesystem lock. But for now, I've renamed the workspace to unblock the build (the alternative is filing an ASF INFRA ticket to get them to restart the node.) On Mon, Jan 23, 2017 at 2:17 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote:

Re: Build failed in Jenkins: Mesos-Reviewbot-Windows #29

Tweaked the test filters on the job. I'll move this job into the `support/jenkins` folder too. On Fri, Jan 20, 2017 at 12:08 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See > > Changes: > > [alexr] Passed an

Re: Build failed in Jenkins: Mesos-Windows #1077

Oops. I'll fix this, and I'll move the Windows scripts into the `jenkins/...` folder while I'm at it. On Thu, Jan 19, 2017 at 5:44 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See > > Changes: > > [josephwu] CMake:

Re: Build failed in Jenkins: Mesos-Windows #1052

Pushed the fix. I am hopeful that the Windows build will return to "normal" in the next build :) On Fri, Jan 13, 2017 at 4:17 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See > > Changes: > > [bmahler] Added a

Re: Build failed in Jenkins: Mesos-Windows-Reviewbot #9

Disabled for now. I suspect that the timed-out build from earlier left a zombie process around holding onto a file in this directory (which in Windows prevents others from deleting the directory). I'll have to request ASF infra to restart this box.

Re: Build failed in Jenkins: Mesos-Windows-Reviewbot #6

The actual error is buried in the build output: CMake Error at zookeeper-06d3f3f-stamp/extract-zookeeper-06d3f3f.cmake:50 (file): file RENAME failed to rename

Re: Build failed in Jenkins: Mesos-Windows #1051

This build actually succeeded, but it looks like batch reports the exit code in an odd way. I'll fix this up. On Thu, Jan 12, 2017 at 7:27 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See > > Changes: > > [josephwu]

Re: Build failed in Jenkins: Mesos-Windows-Reviewbot #3

Ignore this, there was a stale CMakeCache on the machine. On Wed, Jan 11, 2017 at 5:55 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See > > -- > Started by user josephwu >

Re: Build failed in Jenkins: Mesos-Windows #990

This build is going to fail (on creating symlinks) for a little bit. On Windows, you must be an Admin (i.e. root) to create symlinks and there doesn't appear to be a workable exception to this rule in released (i.e. outside of Microsoft) builds of Windows. We will likely never get this

Re: Build failed in Jenkins: Mesos-Windows #964

Yeah, there's something MSVC doesn't like about this particular usage of an `#ifdef` within a macro. A bunch of other usages are acceptable to MSVC, but not this one. I'll look into it. On Sat, Dec 10, 2016 at 2:43 PM, Alex R wrote: > Greg, is this related to your recent

Re: Build failed in Jenkins: Mesos-Windows #962

Pushed the fix. https://reviews.apache.org/r/54610/ On Fri, Dec 9, 2016 at 5:14 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See > > Changes: > > [bmahler] Updated master and agent endpoints to expose >

Re: Build failed in Jenkins: Mesos-Windows #880

Pushed the fix. On Tue, Nov 29, 2016 at 3:08 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See > > Changes: > > [yujie.jay] Added helper to get the io switchboard server address. > > [josephwu] CMake: Added

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

Oops, looks like two things need to be fixed: * socket_tests should be added to the build. * libmesos's dependency chain doesn't include zookeeper (it was removed accidentally). I'll push the fixes shortly. On Tue, Nov 29, 2016 at 1:53 PM, Apache Jenkins Server < jenk...@builds.apache.org>

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

Pushed the fix. On Tue, Nov 29, 2016 at 11:51 AM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See COMPILER=gcc,CONFIGURATION=--verbose%20--enable-libevent% > 20--enable-ssl,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS= >

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)&&(!ubuntu-6)&&(!ubuntu-eu2) #2983

Pushed the fix. (Added hook.proto to the build) On Mon, Nov 28, 2016 at 9:24 AM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See COMPILER=gcc,CONFIGURATION=--verbose%20--enable-libevent% >

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

Pushed a fix. Apparently, the CMake build was not patching the http_parser header (like we do in the automake build). On Wed, Nov 23, 2016 at 2:12 PM, Joseph Wu <jos...@mesosphere.io> wrote: > Looking into this... > > On Wed, Nov 23, 2016 at 2:11 PM, Apache Jenkins

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

Looking into this... On Wed, Nov 23, 2016 at 2:11 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See COMPILER=gcc,CONFIGURATION=--verbose%20--enable-libevent% > 20--enable-ssl,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS= >

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

Alex, just to follow up, can you tweak and/or revert the test parts of your backports? `make check` on the 0.28.x branch should still succeed. On Wed, Nov 9, 2016 at 10:08 AM, Joseph Wu <jos...@mesosphere.io> wrote: > Looks like the CI ran a build on your backported branch. You

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

Looks like the CI ran a build on your backported branch. You possibly backported some tests, which included helpers that don't exist in the backport branches. On Wed, Nov 9, 2016 at 5:05 AM, Alex R wrote: > I don't quite understand what has happened there. Looks as if the

Re: Build failed in Jenkins: Mesos-Windows #811

I'm discussing the fix in the Mesos Slack. Essentially, some Linux-specific syscalls were not #ifdef'd to Linux. And it just so happens that Windows is our only non-Linux CI platform. On Mon, Nov 7, 2016 at 11:09 AM, Vinod Kone wrote: > joseph? > > On Mon, Nov 7, 2016 at

Re: Build failed in Jenkins: Mesos-Windows #703

on) create symlinks. On Mon, Oct 17, 2016 at 11:08 AM, Vinod Kone <vinodk...@apache.org> wrote: > Can the stout tests be prefixed with `ROOT_` ? > > On Fri, Oct 14, 2016 at 5:15 PM, Joseph Wu <jos...@mesosphere.io> wrote: > > > I'll fix this shortly. I need to disable

Re: Build failed in Jenkins: Mesos-Windows #691

Pushed a fix. On Thu, Oct 13, 2016 at 5:10 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See > > Changes: > > [xujyan] Added MESOS-3421 to 1.1.0 CHANGELOG. > > -- > [...truncated

Re: Build failed in Jenkins: Mesos-Windows #679

I'll be pushing a fix for this shortly! On Wed, Oct 12, 2016 at 12:54 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See > > Changes: > > [yujie.jay] Added a test for verifying nested container environment. > >

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

Looks like virtualenv is not installed on all the machines reviewbot can run on. I'll see about fixing this. On Mon, Oct 10, 2016 at 1:03 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See > >

Re: Build failed in Jenkins: Mesos-Windows #636

Looks like a network (DNS) blip during the build. I'll schedule a rebuild. On Mon, Oct 3, 2016 at 5:22 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See > > Changes: > > [vinodkone] Cleaned up some code for managing

Re: Build failed in Jenkins: Mesos-Windows-Reviewbot #2

Oops, apparently python isn't installed on the Windows build box in ASF. I'll disable this build until it is. On Fri, Sep 30, 2016 at 6:20 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See > > Changes: > >

Re: Build failed in Jenkins: Mesos-Windows #577

Oops, my bad. Fixed! On Fri, Sep 23, 2016 at 7:01 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See > > Changes: > > [josephwu] Fixed OsTest.User test failure due to gids ordering. > > [josephwu] Windows: Fixed warnings

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

Pushed the fix: https://reviews.apache.org/r/52186/ Thanks Guangya! On Thu, Sep 22, 2016 at 7:08 PM, Vinod Kone wrote: > Qian, can you take a look? > > @vinodkone > > > On Sep 22, 2016, at 7:02 PM, Apache Jenkins Server < > jenk...@builds.apache.org> wrote: > > > > See

Re: Build failed in Jenkins: Mesos-Windows #551

Posted a fix here: https://reviews.apache.org/r/52129/ On Wed, Sep 21, 2016 at 12:15 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See > > Changes: > > [yujie.jay] Adjusted the comment to avoid using sub-containers. > >

Re: Build failed in Jenkins: Mesos-Windows #497

This was merely missing a header. Pushed the fix. On Tue, Sep 13, 2016 at 11:31 AM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See > > Changes: > > [yujie.jay] Enabled cgroups unified isolator in isolation. > >

Re: Build failed in Jenkins: Mesos-Windows #480

Funny how the Windows CI caught this first :) Already pushed the fix. Thanks Guangya! On Thu, Sep 8, 2016 at 5:16 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See > > Changes: > > [yujie.jay] Supported provisioner

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

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

Pushed a fix. Should be returning to normal shortly... On Tue, Aug 23, 2016 at 1:30 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See > > -- > [...truncated 9583 lines...] >

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

Just pushed the fix. Thanks Haosdent! https://reviews.apache.org/r/51285/ On Sat, Aug 20, 2016 at 11:52 AM, Vinod Kone wrote: > has this been fixed? > > On Sat, Aug 20, 2016 at 9:46 AM, Apache Jenkins Server < > jenk...@builds.apache.org> wrote: > > > See

Re: Build failed in Jenkins: Mesos-Windows #357

Here's the fix: https://reviews.apache.org/r/50964/ On Wed, Aug 10, 2016 at 12:05 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See > > Changes: > > [anand] Removed the redundant `mesos::` namespace prefix + minor style

Re: Build failed in Jenkins: Mesos-Windows #350

Tracked here: https://issues.apache.org/jira/browse/INFRA-12400 On Tue, Aug 9, 2016 at 11:59 AM, Joseph Wu <jos...@mesosphere.io> wrote: > Changed the build config to not fail if /tmp can't be recreated. We > aren't running the tests (yet), so the folder has no effect currently. &g

Re: Build failed in Jenkins: Mesos-Windows #350

Changed the build config to not fail if /tmp can't be recreated. We aren't running the tests (yet), so the folder has no effect currently. I'll check with ASF Infra to see if we can un-protect that folder. Otherwise, the build machine will eventually run out of disk space because test cleanup is

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) #2594

Looks like a flakiness on PyPi: Searching for six>=1.5 > Reading https://pypi.python.org/simple/six/ > Download error on https://pypi.python.org/simple/six/: [Errno 101] > Network is unreachable -- Some packages may not be found! On Mon, Aug 8, 2016 at 3:18 PM, Apache Jenkins Server <

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

I tweaked Haosdent's review so that Reviewbot will not complain about the unpublished review :) On Wed, Aug 3, 2016 at 2:14 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See > > -- >

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

This test fails on a fairly regular basis for me (on OSX). Shuai, could you take a look and triage? On Thu, Jul 21, 2016 at 5:13 PM, Vinod Kone wrote: > @Shuai Looks like you wrote this test? Can you please triage the flaky > test? > > On Thu, Jul 21, 2016 at 5:40 AM,

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) #2564

Looks like it's the one I added. Same underlying problem as this: https://issues.apache.org/jira/browse/MESOS-5907 On Tue, Jul 26, 2016 at 12:26 PM, Vinod Kone wrote: > never ending test? > > On Tue, Jul 26, 2016 at 12:21 PM, Apache Jenkins Server < >

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)&&(!ubuntu-6) #2524

This only affects clean builds on CentOS. Odd thing is, when I added this line [1], I made a clean build on Ubuntu (which worked). Seems like the same build script on CentOS doesn't like the quotations. [1]

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

The CMake build is missing a `-fPIC` linker flag for the libprocess library (which is static by default in this build). I'll push a fix shortly... On Fri, Jul 15, 2016 at 1:57 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See < >

Re: Build failed in Jenkins: Mesos-Windows #256

There's a build-order bug in the CMake build. We're not always generating the protobufs before building the Mesos sources. Srini is working on a fix. On Thu, Jul 14, 2016 at 12:27 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See

Re: Build failed in Jenkins: Mesos-Windows #251

This build isn't completely set up yet, so please treat this as a build email test :) On Tue, Jul 12, 2016 at 3:34 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See > > Changes: > > [josephwu] Added Windows build batch

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

Working on a fix. This is purely a test failure, so it definitely shouldn't block 1.0. JIRA: https://issues.apache.org/jira/browse/MESOS-5759 On Fri, Jul 1, 2016 at 12:04 PM, Vinod Kone wrote: > > On Fri, Jul 1, 2016 at 11:11 AM, Apache Jenkins Server < >

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

Looking into the test failure: https://issues.apache.org/jira/browse/MESOS-5759 The build timing out is possibly related, as the last log timestamp is 20:17:01 and the build started at approx. 19:48:50. It seems to have sat waiting on the libprocess test global cleanup. On Thu, Jun 30, 2016 at

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

Pushed a fix. I forgot to add a dependency between the test binaries, so they were being built in a random order. On Thu, Jun 30, 2016 at 12:06 AM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See < >

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

This isn't related to the test refactor. Looks like this was flaky before :( The problem is fairly trivial though. Filed: https://issues.apache.org/jira/browse/MESOS-4961 On Wed, Mar 16, 2016 at 7:34 AM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See < >

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

This appears to be related to the recent test speedup. Filed: https://issues.apache.org/jira/browse/MESOS-4768 On Wed, Feb 24, 2016 at 2:39 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See < >

Re: Build failed in Jenkins: Mesos » gcc,--verbose,GLOG_v=1 MESOS_VERBOSE=1,centos:7,docker||Hadoop #1599

There doesn't seem to be a JIRA tracking this, so I filed this one: https://issues.apache.org/jira/browse/MESOS-4574 On Sun, Jan 31, 2016 at 10:37 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 #1585

Looks like this is the same problem as https://issues.apache.org/jira/browse/MESOS-4554 On Fri, Jan 29, 2016 at 11:28 AM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See < >

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

This problem is tracked here: https://issues.apache.org/jira/browse/MESOS-3273 On Thu, Dec 17, 2015 at 8:16 AM, 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 #1346

, Joseph Wu <jos...@mesosphere.io> wrote: > Note: Jojy, Gilbert, and I are looking into why > RegistryClientTest.SimpleGetManifest is stalling. > > On Thu, Dec 10, 2015 at 12:32 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 #1346

Note: Jojy, Gilbert, and I are looking into why RegistryClientTest.SimpleGetManifest is stalling. On Thu, Dec 10, 2015 at 12:32 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 #1347

Note: These last three build failures were already "fixed" here: https://github.com/apache/mesos/commit/08aa92b2ae36ed42bb3cf392b0f320a34da5af46 On Thu, Dec 10, 2015 at 5:32 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See < >

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

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,ubuntu:14.04,docker||Hadoop #1323

Wow, this is popping up a lot. Joris will be committing this (partial) fix shortly though! https://issues.apache.org/jira/browse/MESOS-4059 https://reviews.apache.org/r/40935/ On Fri, Dec 4, 2015 at 9:25 AM, 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 #1315

There were a couple of identical build failures, but they all have the same root-flakinesses. There are a total of 3 issues with the test, tracked here: https://issues.apache.org/jira/browse/MESOS-3916 https://issues.apache.org/jira/browse/MESOS-4059 We have fixes (1 committed, 1 in review)

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

Note: This does not appear to be a test timeout (like the other ones we've been seeing). The complete test suite ran for about 10 minutes (I see timestamps from ~17:02:22 to ~17:11:51). The setup/build prior to the tests seem to have taken the remainder of the 300 minutes. On Fri, Dec 4, 2015

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

This specific flakiness is tracked here: https://issues.apache.org/jira/browse/MESOS-4059 On Thu, Dec 3, 2015 at 10:25 AM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See < >

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

This one: https://issues.apache.org/jira/browse/MESOS-3235 On Mon, Nov 9, 2015 at 10:34 AM, Vinod Kone wrote: > On Sun, Nov 8, 2015 at 5:16 AM, Apache Jenkins Server < > jenk...@builds.apache.org> wrote: > > > [ FAILED ] ExamplesTest.PersistentVolumeFramework > > [