You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beam.apache.org by Kenneth Knowles <kl...@google.com.INVALID> on 2017/01/24 04:39:55 UTC
Re: Jenkins build is still unstable: beam_PostCommit_Java_RunnableOnService_Flink
#1424
It looks like there was some downtime in postcommit coverage. So I made a
guess at the PR that might have caused this and started a postcommit run:
https://builds.apache.org/job/beam_PostCommit_Java_RunnableOnService_Flink/1425/
Other guesses welcome, or other styles of investigation too.
On Mon, Jan 23, 2017 at 8:01 PM, Apache Jenkins Server <
jenkins@builds.apache.org> wrote:
> See <https://builds.apache.org/job/beam_PostCommit_Java_
> RunnableOnService_Flink/changes>
>
>
Re: Jenkins build is still unstable: beam_PostCommit_Java_RunnableOnService_Flink
#1424
Posted by Kenneth Knowles <kl...@google.com.INVALID>.
Closing the loop here, I think https://github.com/apache/beam/pull/1839
fixed it up. I'll be better about filing JIRA and assigning so there's no
parallel work next time.
On Wed, Jan 25, 2017 at 6:29 AM, Aljoscha Krettek <al...@apache.org>
wrote:
> I'm investigating (using git bisect).
>
> On Tue, 24 Jan 2017 at 05:40 Kenneth Knowles <kl...@google.com.invalid>
> wrote:
>
> > It looks like there was some downtime in postcommit coverage. So I made a
> > guess at the PR that might have caused this and started a postcommit run:
> >
> > https://builds.apache.org/job/beam_PostCommit_Java_
> RunnableOnService_Flink/1425/
> >
> > Other guesses welcome, or other styles of investigation too.
> >
> > On Mon, Jan 23, 2017 at 8:01 PM, Apache Jenkins Server <
> > jenkins@builds.apache.org> wrote:
> >
> > > See <https://builds.apache.org/job/beam_PostCommit_Java_
> > > RunnableOnService_Flink/changes>
> > >
> > >
> >
>
Re: Jenkins build is still unstable: beam_PostCommit_Java_RunnableOnService_Flink
#1424
Posted by Aljoscha Krettek <al...@apache.org>.
I'm investigating (using git bisect).
On Tue, 24 Jan 2017 at 05:40 Kenneth Knowles <kl...@google.com.invalid> wrote:
> It looks like there was some downtime in postcommit coverage. So I made a
> guess at the PR that might have caused this and started a postcommit run:
>
> https://builds.apache.org/job/beam_PostCommit_Java_RunnableOnService_Flink/1425/
>
> Other guesses welcome, or other styles of investigation too.
>
> On Mon, Jan 23, 2017 at 8:01 PM, Apache Jenkins Server <
> jenkins@builds.apache.org> wrote:
>
> > See <https://builds.apache.org/job/beam_PostCommit_Java_
> > RunnableOnService_Flink/changes>
> >
> >
>