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 <[email protected]> wrote: > 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 <[email protected]> > > To: [email protected], [email protected], [email protected] > > Subject: Jenkins build is still unstable: > > beam_PostCommit_Java_RunnableOnService_Flink #1866 > > Date: Thu, 9 Mar 2017 01:45:13 +0000 (UTC) > > > > See > > <https://builds.apache.org/job/beam_PostCommit_Java_ > RunnableOnService_Flink/1866/display/redirect?page=changes> > > >
