Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BEAM-6512] Fixes flake in GrpcDataServiceTest #7784

Closed

Conversation

TheNeuralBit
Copy link
Member

Synchronizes based on outbound elements rather than inbound, to ensure that we don't make an assertion before the elements have been received in the clients.

Post-Commit Tests Status (on master branch)

Lang SDK Apex Dataflow Flink Gearpump Samza Spark
Go Build Status --- --- --- --- --- ---
Java Build Status Build Status Build Status Build Status
Build Status
Build Status
Build Status Build Status Build Status
Python Build Status --- Build Status
Build Status
Build Status --- --- ---

@TheNeuralBit
Copy link
Member Author

@robertwb could you take a look at this? I chatted a bit with Thomas Groh who wrote the original test, and he said you'd be the most knowledgeable about this.

I'm a little concerned that explicitly waiting for exactly three calls to onNext could be cheating - e.g. is it possible for it to be called >3 times and we should call that a test failure?

FYI - here's a gradle scan with some more detailed logging from the original flake

@TheNeuralBit
Copy link
Member Author

Closing in favor of #7794

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant