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/28 16:59:00 UTC

[jira] [Commented] (BEAM-13952) Dataflow streaming tests failing new AfterSynchronizedProcessingTime test

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

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

This issue is assigned but has not received an update in 30 days so it has been labeled "stale-assigned". If you are still working on the issue, please give an update and remove the label. If you are no longer working on the issue, please unassign so someone else may work on it. In 7 days the issue will be automatically unassigned.

> Dataflow streaming tests failing new AfterSynchronizedProcessingTime test
> -------------------------------------------------------------------------
>
>                 Key: BEAM-13952
>                 URL: https://issues.apache.org/jira/browse/BEAM-13952
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-dataflow, test-failures
>            Reporter: Kenneth Knowles
>            Assignee: Kenneth Knowles
>            Priority: P1
>              Labels: currently-failing, stale-assigned
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> The new test {{org.apache.beam.sdk.transforms.GroupByKeyTest$BasicTests.testAfterProcessingTimeContinuationTriggerUsingState}} is failing on Dataflow streaming. Most likely the delays are not large enough for Dataflow's bundle latency, so the triggering does not occur early.
> https://ci-beam.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Dataflow_Streaming/1876/testReport/junit/org.apache.beam.sdk.transforms/GroupByKeyTest$BasicTests/testAfterProcessingTimeContinuationTriggerUsingState/



--
This message was sent by Atlassian Jira
(v8.20.1#820001)