You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2019/11/02 20:41:00 UTC

[jira] [Commented] (BEAM-8459) Samza runner fails UsesStrictTimerOrdering category tests

    [ https://issues.apache.org/jira/browse/BEAM-8459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16965498#comment-16965498 ] 

Kenneth Knowles commented on BEAM-8459:
---------------------------------------

It affects enough prior versions that I'm not sure it is worth noting them. Feel free to add them back. But I don't want to list just one version which could make it look like a regression, or could make users of other versions miss the issue.

> Samza runner fails UsesStrictTimerOrdering category tests
> ---------------------------------------------------------
>
>                 Key: BEAM-8459
>                 URL: https://issues.apache.org/jira/browse/BEAM-8459
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-samza
>            Reporter: Jan Lukavský
>            Assignee: Xinyu Liu
>            Priority: Major
>
> BEAM-7520 introduced new set of validatesRunner tests that test that timers are fired exactly in order of increasing timestamp. Samza runner fails these added tests (are currently ignored).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)