[jira] [Commented] (BEAM-14193) SpannerChangeStreamOrderedWithinKeyGloballyIT and SpannerChangeStreamOrderedWithinKeyIT fail on Direct Runner

["Beam JIRA Bot (Jira)" <ji...@apache.org>]

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

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

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.

> SpannerChangeStreamOrderedWithinKeyGloballyIT and SpannerChangeStreamOrderedWithinKeyIT fail on Direct Runner
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: BEAM-14193
>                 URL: https://issues.apache.org/jira/browse/BEAM-14193
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-direct, test-failures
>            Reporter: Luke Cwik
>            Assignee: Pablo Estrada
>            Priority: P2
>              Labels: stale-assigned
>
> Like BEAM-14151, it seems as though DirectRunner fails on these tests pretty consistently:
> {noformat}
> org.apache.beam.sdk.io.gcp.spanner.changestreams.it.SpannerChangeStreamOrderedWithinKeyGloballyIT.testOrderedWithinKey
> org.apache.beam.sdk.io.gcp.spanner.changestreams.it.SpannerChangeStreamOrderedWithinKeyIT.testOrderedWithinKey
> {noformat}
> This has been failing for a few days, occassionally it passes but that could be a fluke that the direct runner executed it in the order that was expected.
> Example failure: https://ci-beam.apache.org/job/beam_PostCommit_Java/8776/



--
This message was sent by Atlassian Jira
(v8.20.7#820007)