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/12/27 06:36:40 UTC
Jenkins build became unstable:
beam_PostCommit_Java_RunnableOnService_Apex #117
See <https://builds.apache.org/job/beam_PostCommit_Java_RunnableOnService_Apex/117/>
Jenkins build is back to stable :
beam_PostCommit_Java_RunnableOnService_Apex #118
Posted by Apache Jenkins Server <je...@builds.apache.org>.
See <https://builds.apache.org/job/beam_PostCommit_Java_RunnableOnService_Apex/118/>
Re: Jenkins build became unstable: beam_PostCommit_Java_RunnableOnService_Apex
#117
Posted by Jason Kuster <ja...@google.com.INVALID>.
Pipeline succeeded when it should have failed (PAssert for a
containsinanyorder on (1, 2, 3, 4) and (2, 1, 3, 4, 7)). Is there a known
issue for this?
On Mon, Dec 26, 2016 at 10:36 PM, Apache Jenkins Server <
jenkins@builds.apache.org> wrote:
> See <https://builds.apache.org/job/beam_PostCommit_Java_
> RunnableOnService_Apex/117/>
>
>
--
-------
Jason Kuster
Apache Beam (Incubating) / Google Cloud Dataflow