Open damccorm opened 2 years ago
So far 100% failure rate, not flaking.
Seems the test is expecting a particular proto class in a mock, so it isn't lining up with expected results
@zoercai @thiagotnunes this test is now a hard failure. It looks like it is caused by the way it uses mocking, even though the results of a retry may be fine.
@nancyxu123
Looks like the mockSpannerService in SpannerChangeStreamErrorTest actually does not taking effect. It also affects current test suite beam_PreCommit_Java_GCP_IO_Direct where org.apache.beam.sdk.io.gcp.spanner.changestreams.SpannerChangeStreamErrorTest.testAbortedExceptionNotRetriedithDefaultsForStreamSqlRetrySettings
costs 5 minutes exactly on success run. The test being success due to real grpc DEADLINE_EXCEEDED.
The same test suite also has high chance of timeout which also possibly due to similar issue.
Reopen the issue for now for mockSpannerService not working properly
Example failures:
Imported from Jira BEAM-14152. Original Jira may contain additional context. Reported by: lcwik.