[
https://issues.apache.org/jira/browse/BEAM-8460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17474343#comment-17474343
]
Jan Lukavský commented on BEAM-8460:
------------------------------------
Um, this is an old one. :)
IIRC this was resolved by [~mxm] (and the associated PR looks like it enabled
the associated validates runner tests), so I'm marking this as resolved.
> Flink/Spark runner ignores UsesStrictTimerOrdering category tests
> -----------------------------------------------------------------
>
> Key: BEAM-8460
> URL: https://issues.apache.org/jira/browse/BEAM-8460
> Project: Beam
> Issue Type: Bug
> Components: runner-flink, runner-spark
> Affects Versions: 2.17.0
> Reporter: Jan Lukavský
> Priority: P3
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> BEAM-7520 introduced new set of validatesRunner tests that test that timers
> are fired exactly in order of increasing timestamp. Portable Flink runner
> fails these added tests (are currently ignored).
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
