[Failing Test]: Re-enable the skipped Change Stream Unit tests after refactor test code

[jiangzzhu]

What happened?

Re-enable the following temporary disabled unit tests.

SpannerChangeStreamErrorTest > testResourceExhaustedRetry FAILED
java.lang.AssertionError at MatcherAssert.java:18

SpannerChangeStreamErrorTest > testInvalidRecordReceived FAILED
java.lang.AssertionError at MatcherAssert.java:18

SpannerChangeStreamErrorTest > testUnavailableExceptionRetries FAILED
java.lang.AssertionError at MatcherAssert.java:18

SpannerChangeStreamErrorTest > testAbortedExceptionRetries FAILED
java.lang.AssertionError at MatcherAssert.java:18

Issue Failure

Failure: Test is flaky

Issue Priority

Priority: 1 (unhealthy code / failing or flaky postcommit so we cannot be sure 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

[prabalpatkar558412-collab]

Hi @jiangzzhu,
Thanks for flagging this and for listing the specific failing tests.

I’d be interested in taking a look at this. I can help investigate why these assertions started failing after the refactor (e.g., matcher expectations vs. updated behavior, timing/retry semantics), stabilize the tests, and re-enable them safely.

If no one is actively working on this yet, I’m happy to take it on.
Please let me know and feel free to assign it to me.

Thanks!

[shunping]

Hey @prabalpatkar558412-collab, thanks for your interest in this issue. I have assigned it to you.