You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Valentyn Tymofieiev (JIRA)" <ji...@apache.org> on 2019/04/30 18:39:00 UTC
[jira] [Updated] (BEAM-5709) Tests in BeamFnControlServiceTest are
flaky.
[ https://issues.apache.org/jira/browse/BEAM-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Valentyn Tymofieiev updated BEAM-5709:
--------------------------------------
Priority: Critical (was: Minor)
> 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: Critical
> 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)