You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by Apache Jenkins Server <je...@builds.apache.org> on 2017/02/01 01:48:29 UTC
Jenkins build became unstable:
beam_PostCommit_Java_RunnableOnService_Apex #363
See <https://builds.apache.org/job/beam_PostCommit_Java_RunnableOnService_Apex/363/changes>
Re: Jenkins build became unstable: beam_PostCommit_Java_RunnableOnService_Apex
#363
Posted by Kenneth Knowles <kl...@google.com.INVALID>.
Yes, this looks like a real failure. Please do file a JIRA.
On Tue, Jan 31, 2017 at 10:03 PM, Jason Kuster <
jasonkuster@google.com.invalid> wrote:
> This seems like it could be a legitimate flake.
>
> Expected: <1970-01-01T00:09:59.999Z>
> but: was <2017-02-01T01:38:42.261Z>
>
>
> Anyone with more knowledge about the apex runner have any ideas?
>
> On Tue, Jan 31, 2017 at 5:48 PM, Apache Jenkins Server <
> jenkins@builds.apache.org> wrote:
>
> > See <https://builds.apache.org/job/beam_PostCommit_Java_
> > RunnableOnService_Apex/363/changes>
> >
> >
>
>
> --
> -------
> Jason Kuster
> Apache Beam / Google Cloud Dataflow
>
Re: Jenkins build became unstable: beam_PostCommit_Java_RunnableOnService_Apex
#363
Posted by Jason Kuster <ja...@google.com.INVALID>.
This seems like it could be a legitimate flake.
Expected: <1970-01-01T00:09:59.999Z>
but: was <2017-02-01T01:38:42.261Z>
Anyone with more knowledge about the apex runner have any ideas?
On Tue, Jan 31, 2017 at 5:48 PM, Apache Jenkins Server <
jenkins@builds.apache.org> wrote:
> See <https://builds.apache.org/job/beam_PostCommit_Java_
> RunnableOnService_Apex/363/changes>
>
>
--
-------
Jason Kuster
Apache Beam / Google Cloud Dataflow
Jenkins build is back to stable :
beam_PostCommit_Java_RunnableOnService_Apex #364
Posted by Apache Jenkins Server <je...@builds.apache.org>.
See <https://builds.apache.org/job/beam_PostCommit_Java_RunnableOnService_Apex/364/changes>