Basically, what you did is perfect IMO. To pin it down, I think I've roughly been following this procedure:
1. Notice break and email list "I'm investigating", maybe plus in some relevant people. 2. Attempt to identify cause of break, file JIRA. If cannot diagnose relatively quickly, file JIRA with request for help. 3. some communication, work, testing... a wild fix appears! 4. Review and merge. Which is pretty much what you've done. So, thanks!! Dan On Fri, Nov 11, 2016 at 2:57 PM, Aljoscha Krettek <[email protected]> wrote: > This looks like it was introduced by the new commit mentioned here but it's > actually caused by a pre-existing (unknown) bug in the Flink runner: > https://issues.apache.org/jira/browse/BEAM-965. > > I also have a fix ready. > > Btw, how should we deal with these messages from Jenkins? I'm writing to > the dev list so that no-one else spends the energy for looking into this. > > ---------- Forwarded message --------- > From: Apache Jenkins Server <[email protected]> > Date: Fri, 11 Nov 2016 at 20:17 > Subject: Jenkins build became unstable: > beam_PostCommit_RunnableOnService_FlinkLocal #813 > To: <[email protected]>, <[email protected]> > > > See < > https://builds.apache.org/job/beam_PostCommit_ > RunnableOnService_FlinkLocal/813/changes > > >
