[ 
https://issues.apache.org/jira/browse/BEAM-9382?focusedWorklogId=400976&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-400976
 ]

ASF GitHub Bot logged work on BEAM-9382:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 10/Mar/20 20:05
            Start Date: 10/Mar/20 20:05
    Worklog Time Spent: 10m 
      Work Description: acrites commented on issue #10988: [BEAM-9382] Clean up 
of TestStreamTranscriptTests.
URL: https://github.com/apache/beam/pull/10988#issuecomment-597287538
 
 
   It looks like TriggerDriverTranscriptTest.test_early_late_sessions is 
failing (since there's no way to sickbay that test). Am I understanding the 
semantics of PaneInfo index correctly? The first firing of each window should 
have index 0 even if that window was the result of merging another window, 
right?
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 400976)
    Time Spent: 1h 50m  (was: 1h 40m)

> TestStreamTranscriptTest relies on non-deterministic behavior
> -------------------------------------------------------------
>
>                 Key: BEAM-9382
>                 URL: https://issues.apache.org/jira/browse/BEAM-9382
>             Project: Beam
>          Issue Type: Bug
>          Components: testing
>            Reporter: Andrew Crites
>            Assignee: Andrew Crites
>            Priority: Minor
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> The test discarding_early_fixed uses an early trigger Count(2) and then 
> inserts 3 elements, assuming all 3 will get emitted in the early pane. 
> However, runners do not have to follow this behavior. Instead, they could 
> emit the first two elements seen and then buffer the third until something 
> else comes in. We should change this test to only insert 2 elements so that 
> all runners will behave the same.



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

Reply via email to