You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beam.apache.org by Jason Kuster <ja...@google.com.INVALID> on 2016/12/27 19:10:16 UTC
Re: Jenkins build became unstable: beam_PostCommit_Java_RunnableOnService_Apex
#119
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 Tue, Dec 27, 2016 at 10:06 AM, Apache Jenkins Server <
jenkins@builds.apache.org> wrote:
> See <https://builds.apache.org/job/beam_PostCommit_Java_
> RunnableOnService_Apex/119/changes>
>
>
--
-------
Jason Kuster
Apache Beam (Incubating) / Google Cloud Dataflow
Re: Jenkins build became unstable: beam_PostCommit_Java_RunnableOnService_Apex
#119
Posted by Jason Kuster <ja...@google.com.INVALID>.
Error is
Expected: <1970-01-01T00:00:00.000Z>
but: was <2016-12-27T17:53:23.629Z>
2016-12-27T17:53:23.629Z is the time the test was run. Looks like it
could be an actual issue?
On Tue, Dec 27, 2016 at 11:11 AM, Jason Kuster <ja...@google.com>
wrote:
> Sorry, this is for #117. Moving there, investigating #119.
>
> On Tue, Dec 27, 2016 at 11:10 AM, Jason Kuster <ja...@google.com>
> wrote:
>
>> 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 Tue, Dec 27, 2016 at 10:06 AM, Apache Jenkins Server <
>> jenkins@builds.apache.org> wrote:
>>
>>> See <https://builds.apache.org/job/beam_PostCommit_Java_Runnable
>>> OnService_Apex/119/changes>
>>>
>>>
>>
>>
>> --
>> -------
>> Jason Kuster
>> Apache Beam (Incubating) / Google Cloud Dataflow
>>
>
>
>
> --
> -------
> Jason Kuster
> Apache Beam (Incubating) / Google Cloud Dataflow
>
--
-------
Jason Kuster
Apache Beam (Incubating) / Google Cloud Dataflow
Re: Jenkins build became unstable: beam_PostCommit_Java_RunnableOnService_Apex
#119
Posted by Jason Kuster <ja...@google.com.INVALID>.
Sorry, this is for #117. Moving there, investigating #119.
On Tue, Dec 27, 2016 at 11:10 AM, Jason Kuster <ja...@google.com>
wrote:
> 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 Tue, Dec 27, 2016 at 10:06 AM, Apache Jenkins Server <
> jenkins@builds.apache.org> wrote:
>
>> See <https://builds.apache.org/job/beam_PostCommit_Java_Runnable
>> OnService_Apex/119/changes>
>>
>>
>
>
> --
> -------
> Jason Kuster
> Apache Beam (Incubating) / Google Cloud Dataflow
>
--
-------
Jason Kuster
Apache Beam (Incubating) / Google Cloud Dataflow