[
https://issues.apache.org/jira/browse/BEAM-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16830566#comment-16830566
]
Valentyn Tymofieiev commented on BEAM-5709:
-------------------------------------------
The test remains to be flaky - I saw at least two flakes today, example:
https://builds.apache.org/job/beam_PreCommit_Java_Phrase/1056/testReport/org.apache.beam.runners.dataflow.worker.fn/BeamFnControlServiceTest/testClientConnecting/
> Tests in BeamFnControlServiceTest are flaky.
> --------------------------------------------
>
> Key: BEAM-5709
> URL: https://issues.apache.org/jira/browse/BEAM-5709
> Project: Beam
> Issue Type: Bug
> Components: runner-dataflow
> Reporter: Daniel Oliveira
> Assignee: Daniel Oliveira
> Priority: Minor
> Fix For: Not applicable
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> https://github.com/apache/beam/blob/master/runners/google-cloud-dataflow-java/worker/src/test/java/org/apache/beam/runners/dataflow/worker/fn/BeamFnControlServiceTest.java
> Tests for BeamFnControlService are currently flaky. The test attempts to
> verify that onCompleted was called on the mock streams, but that function
> gets called on a separate thread, so occasionally the function will not have
> been called yet, despite the server being shut down.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
