mxtymoshyk commented on issue #32047: URL: https://github.com/apache/beam/issues/32047#issuecomment-6445414003
I couldn't reproduce this. I looked at the last 100 runs each of `beam_PostCommit_Java_DataflowV2` and `beam_PostCommit_Java_DataflowV1` (Sep 25 to Oct 27, 2026). V2 had 41 failed runs and V1 had 35. The `Expected: <2L> but: was <1L>` assertion didn't appear in any of them. `BigtableWriteIT` failed twice in that window: - V2, Oct 25 ([run 40159416000](https://github.com/apache/beam/actions/runs/40159416000)): `Error while staging packages` - V1, Oct 15 ([run 38728496633](https://github.com/apache/beam/actions/runs/38728496633)): `Staged package ... tests-...jar` Both 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. -- 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]
