[jira] [Updated] (BEAM-1796) Apex ValidatesRunner fails on testShiftTimestampInvalid

["Kenneth Knowles (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/BEAM-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kenneth Knowles updated BEAM-1796:
----------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Resolved)

Hello! Due to a bug in our Jira configuration, this issue had status:Resolved but resolution:Unresolved.

I am bulk editing these issues to have resolution:Fixed

If a different resolution is appropriate, please change it. To do this, click the "Resolve" button (you can do this even for closed issues) and set the Resolution field to the right value.

> Apex ValidatesRunner fails on testShiftTimestampInvalid
> -------------------------------------------------------
>
>                 Key: BEAM-1796
>                 URL: https://issues.apache.org/jira/browse/BEAM-1796
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-apex
>            Reporter: Thomas Groh
>            Priority: P3
>
> The failing test should fail due to an exception, but the pipeline appears to either succeed or fail silently. Once the pipeline fails appropriately, the test should be moved to be {{RunnableOnService}}
> There are exceptions with timestamps equal to now as the element timestamps within the logs, which should not be present - all elements should begin with timestamps equal to BoundedWindow.TIMESTAMP_MIN_VALUE, and shift only when specified.
> https://builds.apache.org/job/beam_PostCommit_Java_RunnableOnService_Apex/843/org.apache.beam$beam-runners-apex/testReport/org.apache.beam.sdk.transforms/ParDoTest/testParDoShiftTimestampInvalid/



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