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 <
[email protected]> wrote:

> See <https://builds.apache.org/job/beam_PostCommit_Java_
> RunnableOnService_Apex/363/changes>
>
>


-- 
-------
Jason Kuster
Apache Beam / Google Cloud Dataflow

Reply via email to