Re: Fwd: Jenkins build is still unstable: beam_PostCommit_Java_RunnableOnService_Flink #1866

2017-03-09 Thread Kenneth Knowles
I commented there, but in the meantime I suggest suppressing the UsesTimersInParDo test category. You lose some coverage on tests that were passing, but they are tests of a feature that is probably not really safe to use. On Thu, Mar 9, 2017 at 7:17 AM, Aljoscha Krettek wrote: > Figured out what

Re: Fwd: Jenkins build is still unstable: beam_PostCommit_Java_RunnableOnService_Flink #1866

2017-03-09 Thread Aljoscha Krettek
Figured out what it is: https://issues.apache.org/jira/browse/BEAM-1674 Unfortunately, I don't have a solution right now. On Thu, Mar 9, 2017, at 11:36, Aljoscha Krettek wrote: > I'm looking into the recent streak of unstable builds. > > - Original message - > From: Apache Jenkins Server

Fwd: Jenkins build is still unstable: beam_PostCommit_Java_RunnableOnService_Flink #1866

2017-03-09 Thread Aljoscha Krettek
I'm looking into the recent streak of unstable builds. - Original message - From: Apache Jenkins Server To: comm...@beam.apache.org, k...@google.com, al...@google.com Subject: Jenkins build is still unstable: beam_PostCommit_Java_RunnableOnService_Flink #1866 Date: Thu, 9 Mar 2017 01:45:1