[
https://issues.apache.org/jira/browse/BEAM-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kenneth Knowles updated BEAM-1796:
----------------------------------
Summary: Apex ValidatesRunner fails on testShiftTimestampInvalid (was:
Apex RunnableOnService fails on testShiftTimestampInvalid)
> 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
>
> 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
(v6.3.15#6346)
