Failing build

["Zeolla@GMail.com" <ze...@gmail.com>]

We appear to have a failed build again:

No output has been received in the last 10m0s, this potentially indicates a
stalled build or something wrong with the build itself.

https://travis-ci.org/apache/incubator-metron/builds/219261745

Jon
-- 

Jon

Re: Failing build

[Otto Fowler <ot...@gmail.com>]

Maybe it is a container thing?  I don’t think my PR for extensions has the
problem,
or has had it in my travis - and it is a vm in travis.



On April 20, 2017 at 09:06:21, Casey Stella (cestella@gmail.com) wrote:

oh man, yeah, it's pissing me off too. I'm still looking at ways to get
around Storm to not have its slots jam up at the end of tests. It's
particularly bad because it just doesn't seem to happen to me locally.
Also, while it does happen periodically on my personal travis, it's way
more infrequent . At this point, I'm going to try to spin the in memory
components up once and then reuse them across the parser integration tests,
which is mostly where I see the problem occurring. That would at least get
us closer to being able to run against external infrastructure (i.e. docker
images). It's just been slow going since it's a night and weekend project.

Anyway, if anyone else wants to tackle it, do chime in; I'd be willing to
give it up. ;)

On Wed, Apr 19, 2017 at 9:56 PM, Zeolla@GMail.com <ze...@gmail.com> wrote:

> I was just looking at the commit history and noticed that out of the last
> commits that had travis runs, at least 7 of them failed (mine is still
> running). Given that we require a clean build on the branch prior to
> merging, that's a pretty unfortunate track record.
>
> Jon
>
> On Thu, Apr 6, 2017 at 1:31 PM Casey Stella <ce...@gmail.com> wrote:
>
> > Yeah, this is an intermittent test failure and has to do with the
> migration
> > to storm 1.0.3 and how it handles shutting down in local mode. The slot
> > worker refuses to shut down and freezes and therefore we wait forever.
I
> > thought I had it fixed by manually clobbering the slots, but alas it
> > appears that I only made the problem less frequent. When I found it as
> > part of METRON-793, I ran the fix 20 times locally as well as at least
10
> > times on my personal travis without repetition.
> >
> > Bottom line: we should correct it. I'll have to think a bit more about
> how
> > to fix it and if anyone else wants to take a crack at it, feel free. :)
> >
> > On Thu, Apr 6, 2017 at 1:26 PM, Zeolla@GMail.com <ze...@gmail.com>
> wrote:
> >
> > > We appear to have a failed build again:
> > >
> > > No output has been received in the last 10m0s, this potentially
> > indicates a
> > > stalled build or something wrong with the build itself.
> > >
> > > https://travis-ci.org/apache/incubator-metron/builds/219261745
> > >
> > > Jon
> > > --
> > >
> > > Jon
> > >
> >
> --
>
> Jon
>

Re: Failing build

[Casey Stella <ce...@gmail.com>]

oh man, yeah, it's pissing me off too.  I'm still looking at ways to get
around Storm to not have its slots jam up at the end of tests.  It's
particularly bad because it just doesn't seem to happen to me locally.
Also, while it does happen periodically on my personal travis, it's way
more infrequent .  At this point, I'm going to try to spin the in memory
components up once and then reuse them across the parser integration tests,
which is mostly where I see the problem occurring. That would at least get
us closer to being able to run against external infrastructure (i.e. docker
images).  It's just been slow going since it's a night and weekend project.

Anyway, if anyone else wants to tackle it, do chime in; I'd be willing to
give it up. ;)

On Wed, Apr 19, 2017 at 9:56 PM, Zeolla@GMail.com <ze...@gmail.com> wrote:

> I was just looking at the commit history and noticed that out of the last
> commits that had travis runs, at least 7 of them failed (mine is still
> running).  Given that we require a clean build on the branch prior to
> merging, that's a pretty unfortunate track record.
>
> Jon
>
> On Thu, Apr 6, 2017 at 1:31 PM Casey Stella <ce...@gmail.com> wrote:
>
> > Yeah, this is an intermittent test failure and has to do with the
> migration
> > to storm 1.0.3 and how it handles shutting down in local mode.  The slot
> > worker refuses to shut down and freezes and therefore we wait forever.  I
> > thought I had it fixed by manually clobbering the slots, but alas it
> > appears that I only made the problem less frequent.  When I found it as
> > part of METRON-793, I ran the fix 20 times locally as well as at least 10
> > times on my personal travis without repetition.
> >
> > Bottom line: we should correct it.  I'll have to think a bit more about
> how
> > to fix it and if anyone else wants to take a crack at it, feel free. :)
> >
> > On Thu, Apr 6, 2017 at 1:26 PM, Zeolla@GMail.com <ze...@gmail.com>
> wrote:
> >
> > > We appear to have a failed build again:
> > >
> > > No output has been received in the last 10m0s, this potentially
> > indicates a
> > > stalled build or something wrong with the build itself.
> > >
> > > https://travis-ci.org/apache/incubator-metron/builds/219261745
> > >
> > > Jon
> > > --
> > >
> > > Jon
> > >
> >
> --
>
> Jon
>

Re: Failing build

["Zeolla@GMail.com" <ze...@gmail.com>]

I was just looking at the commit history and noticed that out of the last
commits that had travis runs, at least 7 of them failed (mine is still
running).  Given that we require a clean build on the branch prior to
merging, that's a pretty unfortunate track record.

Jon

On Thu, Apr 6, 2017 at 1:31 PM Casey Stella <ce...@gmail.com> wrote:

> Yeah, this is an intermittent test failure and has to do with the migration
> to storm 1.0.3 and how it handles shutting down in local mode.  The slot
> worker refuses to shut down and freezes and therefore we wait forever.  I
> thought I had it fixed by manually clobbering the slots, but alas it
> appears that I only made the problem less frequent.  When I found it as
> part of METRON-793, I ran the fix 20 times locally as well as at least 10
> times on my personal travis without repetition.
>
> Bottom line: we should correct it.  I'll have to think a bit more about how
> to fix it and if anyone else wants to take a crack at it, feel free. :)
>
> On Thu, Apr 6, 2017 at 1:26 PM, Zeolla@GMail.com <ze...@gmail.com> wrote:
>
> > We appear to have a failed build again:
> >
> > No output has been received in the last 10m0s, this potentially
> indicates a
> > stalled build or something wrong with the build itself.
> >
> > https://travis-ci.org/apache/incubator-metron/builds/219261745
> >
> > Jon
> > --
> >
> > Jon
> >
>
-- 

Jon

Re: Failing build

[Casey Stella <ce...@gmail.com>]

Yeah, this is an intermittent test failure and has to do with the migration
to storm 1.0.3 and how it handles shutting down in local mode.  The slot
worker refuses to shut down and freezes and therefore we wait forever.  I
thought I had it fixed by manually clobbering the slots, but alas it
appears that I only made the problem less frequent.  When I found it as
part of METRON-793, I ran the fix 20 times locally as well as at least 10
times on my personal travis without repetition.

Bottom line: we should correct it.  I'll have to think a bit more about how
to fix it and if anyone else wants to take a crack at it, feel free. :)

On Thu, Apr 6, 2017 at 1:26 PM, Zeolla@GMail.com <ze...@gmail.com> wrote:

> We appear to have a failed build again:
>
> No output has been received in the last 10m0s, this potentially indicates a
> stalled build or something wrong with the build itself.
>
> https://travis-ci.org/apache/incubator-metron/builds/219261745
>
> Jon
> --
>
> Jon
>