[ 
https://issues.apache.org/jira/browse/BEAM-7733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16884098#comment-16884098
 ] 

Kasia Kucharczyk edited comment on BEAM-7733 at 7/12/19 7:10 PM:
-----------------------------------------------------------------

[~altay] I found this [issue|ihttps://ssues.apache.org/jira/browse/BEAM-5529] 
and I thought you may know if it's something similar? Otherwise it's probably 
infra issue.


was (Author: kasiak):
[~altay] I found this [issue|issues.apache.org/jira/browse/BEAM-5529] and I 
thought you may know if it's something similar? Otherwise it's probably infra 
issue.

> Flaky tests on Dataflow because of not found information about job state
> ------------------------------------------------------------------------
>
>                 Key: BEAM-7733
>                 URL: https://issues.apache.org/jira/browse/BEAM-7733
>             Project: Beam
>          Issue Type: Bug
>          Components: testing
>            Reporter: Kasia Kucharczyk
>            Priority: Major
>
> Some of Python performance cron tests on Dataflow experience some problems 
> because of: 
> {code:java}
> AssertionError: Job did not reach to a terminal state after waiting 
> indefinitely.
> {code}
>  
> Dataflow returns following errors: 
> {code:java}
> "error": {
>      "code": 404,
>      "message": "(bf55d279f24d1255): Information about job 
> 2019-07-07_08_42_42-8241186059035490445 could not be found in our system. 
> Please double check the id is correct. If it is please contact customer 
> support.",
>      "status": "NOT_FOUND"
>    }
>  }
> {code}
> Those tests are success on Dataflow, but Jenkins returns failure. 
> It already happened in Combine and CoGroupByKey tests:
>  * [example of Combine 
> test|https://builds.apache.org/view/A-D/view/Beam/view/All/job/beam_LoadTests_Python_Combine_Dataflow_Batch/6/console]
>  * [example of 
> CoGBK|https://builds.apache.org/view/A-D/view/Beam/view/All/job/beam_LoadTests_Python_CoGBK_Dataflow_Batch/3/console]



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Reply via email to