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 2016/06/08 07:00:55 UTC
Jenkins build is still unstable:
beam_PostCommit_RunnableOnService_GoogleCloudDataflow #500
See <https://builds.apache.org/job/beam_PostCommit_RunnableOnService_GoogleCloudDataflow/changes>
Jenkins build is back to stable :
beam_PostCommit_RunnableOnService_GoogleCloudDataflow #504
Posted by Apache Jenkins Server <je...@builds.apache.org>.
See <https://builds.apache.org/job/beam_PostCommit_RunnableOnService_GoogleCloudDataflow/504/>
Jenkins build is still unstable:
beam_PostCommit_RunnableOnService_GoogleCloudDataflow #503
Posted by Apache Jenkins Server <je...@builds.apache.org>.
See <https://builds.apache.org/job/beam_PostCommit_RunnableOnService_GoogleCloudDataflow/changes>
Jenkins build is still unstable:
beam_PostCommit_RunnableOnService_GoogleCloudDataflow #502
Posted by Apache Jenkins Server <je...@builds.apache.org>.
See <https://builds.apache.org/job/beam_PostCommit_RunnableOnService_GoogleCloudDataflow/changes>
Jenkins build is still unstable:
beam_PostCommit_RunnableOnService_GoogleCloudDataflow #501
Posted by Apache Jenkins Server <je...@builds.apache.org>.
See <https://builds.apache.org/job/beam_PostCommit_RunnableOnService_GoogleCloudDataflow/501/>
Re: Jenkins build is still unstable: beam_PostCommit_RunnableOnService_GoogleCloudDataflow
#500
Posted by Dan Halperin <dh...@google.com>.
Just FYI, the jobs are succeeding (thus the tests should be passing), but
verifying that the jobs passed is throwing an exception. There's some other
issue here to be resolved, but there is no issue in the checked-in Beam
code.
On Wed, Jun 8, 2016 at 12:00 AM, Apache Jenkins Server <
jenkins@builds.apache.org> wrote:
> See <
> https://builds.apache.org/job/beam_PostCommit_RunnableOnService_GoogleCloudDataflow/changes
> >
>
>