damccorm opened a new issue, #21424:
URL: https://github.com/apache/beam/issues/21424
Test failures in org.apache.beam.sdk.transforms.ParDoTest in:
* TimestampTests:
[https://ci-beam.apache.org/job/beam_PostCommit_Java_VR_Dataflow_V2_Streaming/1572/](https://ci-beam.apache.org/job/beam_PostCommit_Java_VR_Dataflow_V2_Streaming/1572/)
* OnWindowExpirationTests:
[https://ci-beam.apache.org/job/beam_PostCommit_Java_VR_Dataflow_V2_Streaming/1563/](https://ci-beam.apache.org/job/beam_PostCommit_Java_VR_Dataflow_V2_Streaming/1563/)
These seem to directly correlate to new tests added in:
*
[https://github.com/apache/beam/pull/15540](https://github.com/apache/beam/pull/15540)
*
[https://github.com/apache/beam/pull/15994](https://github.com/apache/beam/pull/15994)
I think the TimestampTests are also failing in
[https://issues.apache.org/jira/projects/BEAM/issues/BEAM-13498,](https://issues.apache.org/jira/projects/BEAM/issues/BEAM-13498,)
so maybe we can use this to track OnWindowExpirationTests failures
My guess is these shouldn't be running for Portable Runner/FnAPI tests.
Imported from Jira
[BEAM-13525](https://issues.apache.org/jira/browse/BEAM-13525). Original Jira
may contain additional context.
Reported by: emilymye.
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
