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

Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/08/10 17:07:22 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=17174620#comment-17174620 ] 

Beam JIRA Bot commented on BEAM-8459:
-------------------------------------

This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.

Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.


> 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ý
>            Priority: P2
>              Labels: stale-P2
>
> 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)