Repository navigation
[Failing Test]: testE2EBigtableWriteWith[...]Failures flaky #32047
Description
What happened?
These error handler tests have long been flaky. For example, in the last 2 weeks, PostCommit Java Dataflow V2 failed 10 times, 6 due to one test failed in these five:
testE2EBigtableWriteWithInvalidColumnFamilyFailures
testE2EBigtableWriteWithEmptyMutationFailures
testE2EBigtableWriteWithEmptyRowFailures
testE2EBigtableWriteWithInvalidTimestampFailures
testE2EBigtableWriteWithOversizedQualifierFailures
Example error:
java.lang.RuntimeException: org.apache.beam.sdk.util.UserCodeException: java.lang.AssertionError: Write to error Sink/Combine/Flatten.PCollections.out:
Expected: <2L>
but: was <1L>
at org.apache.beam.sdk.util.UserCodeException.wrap(UserCodeException.java:39)
at org.apache.beam.sdk.testing.PAssert$DefaultConcludeFn$DoFnInvoker.invokeProcessElement(Unknown Source)
...
Caused by: java.lang.AssertionError: Write to error Sink/Combine/Flatten.PCollections.out:
Expected: <2L>
but: was <1L>
at org.apache.beam.sdk.testing.PAssert$PAssertionSite.capture(PAssert.java:176)
at org.apache.beam.sdk.testing.PAssert.thatSingleton(PAssert.java:499)
at org.apache.beam.sdk.testing.PAssert.thatSingleton(PAssert.java:491)
at org.apache.beam.sdk.io.gcp.bigtable.BigtableWriteIT.failureTest(BigtableWriteIT.java:341)
at org.apache.beam.sdk.io.gcp.bigtable.BigtableWriteIT.testE2EBigtableWriteWithInvalidColumnFamilyFailures(BigtableWriteIT.java:164)
it appears to be related to how elements are bundled, as Dataflow v1 / v2 / direct runner has different flaky rate (Dataflow v2 test fails most frequently)
Issue Failure
Failure: Test is flaky
Issue Priority
Priority: 2 (backlog / disabled test but we think the product is healthy)
Issue Components
- Component: Python SDK
- Component: Java SDK
- Component: Go SDK
- Component: Typescript SDK
- Component: IO connector
- Component: Beam YAML
- Component: Beam examples
- Component: Beam playground
- Component: Beam katas
- Component: Website
- Component: Infrastructure
- Component: Spark Runner
- Component: Flink Runner
- Component: Samza Runner
- Component: Twister2 Runner
- Component: Hazelcast Jet Runner
- Component: Google Cloud Dataflow Runner
Activity
github-actions commentedon Sep 9, 2025
This issue has been marked as stale due to 150 days of inactivity. It will be closed in 30 days if no further activity occurs. If you think that’s incorrect or this issue still needs to be addressed, please simply write any comment. If closed, you can reopen the issue at any time. Thank you for your contributions.
mxtymoshyk commentedon Oct 27, 2026
I couldn't reproduce this. I looked at the last 100 runs each of
beam_PostCommit_Java_DataflowV2andbeam_PostCommit_Java_DataflowV1(Sep 25 to Oct 27, 2026). V2 had 41 failed runs and V1 had 35. TheExpected: <2L> but: was <1L>assertion didn't appear in any of them.BigtableWriteITfailed twice in that window:Error while staging packagesStaged package ... tests-...jarBoth runs failed while uploading packages to GCS, before the job started, so they aren't this bug. When the issue was filed, these tests caused 6 of 10 failed V2 runs over two weeks. Now it's 0 of 41.
The Direct runner suite (
beam_PreCommit_Java_GCP_IO_Direct, 10 failed scheduled runs) shows no failures either.I found no commit that targets this flake. The only recent change to the test file is #40025, a schema fix, so I don't know why the rate dropped.
I think this can be closed. If the failure comes back, please reopen it.
Abacn commentedon Oct 27, 2026
Thanks for investigating it. Close it for now.