You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Mikhail Gryzykhin (JIRA)" <ji...@apache.org> on 2019/03/25 20:22:00 UTC
[jira] [Assigned] (BEAM-6882) [Flake][DF IT tests] job #####
terminated in state UNKNOWN but did not return a failure reason.
[ https://issues.apache.org/jira/browse/BEAM-6882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mikhail Gryzykhin reassigned BEAM-6882:
---------------------------------------
Assignee: Daniel Oliveira
> [Flake][DF IT tests] job ##### terminated in state UNKNOWN but did not return a failure reason.
> -----------------------------------------------------------------------------------------------
>
> Key: BEAM-6882
> URL: https://issues.apache.org/jira/browse/BEAM-6882
> Project: Beam
> Issue Type: Bug
> Components: test-failures, testing
> Reporter: Mikhail Gryzykhin
> Assignee: Daniel Oliveira
> Priority: Critical
> Labels: currently-failing
>
>
> Dataflow integration tests fail regularly failing to properly detect job status. Usually error looks like:
> java.lang.RuntimeException: Dataflow job 2019-03-21_05_08_46-17069693240682025803 terminated in state UNKNOWN but did not return a failure reason. at org.apache.beam.runners.dataflow.TestDataflowRunner.run(TestDataflowRunner.java:134)
> We have several flakes like this a week. (More statistics might be good to add)
> Sample log.
> https://builds.apache.org/job/beam_PostCommit_Java11_ValidatesRunner_PortabilityApi_Dataflow/17/testReport/junit/org.apache.beam.sdk.transforms.windowing/WindowTest/testTimestampCombinerDefault/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)