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 2022/03/13 17:26:00 UTC
[jira] [Commented] (BEAM-13573) Flink runner failing testOnWindowTimestampSkew
[ https://issues.apache.org/jira/browse/BEAM-13573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17505867#comment-17505867 ]
Beam JIRA Bot commented on BEAM-13573:
--------------------------------------
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.
> Flink runner failing testOnWindowTimestampSkew
> ----------------------------------------------
>
> Key: BEAM-13573
> URL: https://issues.apache.org/jira/browse/BEAM-13573
> Project: Beam
> Issue Type: Bug
> Components: runner-flink, test-failures
> Reporter: Kyle Weaver
> Priority: P2
> Labels: sickbay, stale-P2
>
> org.apache.beam.sdk.transforms.ParDoTest$TimestampTests.testOnWindowTimestampSkew
> java.lang.AssertionError: noskew/ParMultiDo(OnWindowExpirationTimestampSkewing).output:
> Expected: iterable with items ["output1970-01-01T00:00:00.006Z"] in any order
> but: not matched: "output1970-01-01T00:00:00.005Z"
--
This message was sent by Atlassian Jira
(v8.20.1#820001)