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

Valentyn Tymofieiev commented on BEAM-8481:
-------------------------------------------

Confirmed that in runs that are timing out, generated protos are not futurized, 
 then Dataflow workers fail to install Beam SDK, whereas on passing runs, the 
generated protos are futurized:

Looked at apache_beam/portability/api/beam_runner_api_pb2.py 

Bad run ([https://builds.apache.org/job/beam_PostCommit_Python37/1000/console,] 
[https://console.cloud.google.com/dataflow/jobsDetail/locations/us-central1/jobs/2019-11-24_10_05_54-6500780864095669452?project=apache-beam-testing],
 
gs://temp-storage-for-end-to-end-tests/staging-it/beamapp-jenkins-1124180539-774412.1574618739.774621/dataflow_python_sdk.tar):
{noformat}
import endpoints_pb2 as endpoints__pb2
{noformat}
 

Good run 
([https://builds.apache.org/job/beam_PostCommit_Python37/1024/console], 
[https://console.cloud.google.com/dataflow/jobsDetail/locations/us-central1/jobs/2019-11-27_17_56_02-3837996942992637611?project=apache-beam-testing],
 
gs://temp-storage-for-end-to-end-tests/staging-it/beamapp-jenkins-1128015551-757858.1574906151.757993/dataflow_python_sdk.tar):
{noformat}
from . import endpoints_pb2 as endpoints__pb2{noformat}

> Python 3.7 Postcommit test -- frequent timeouts
> -----------------------------------------------
>
>                 Key: BEAM-8481
>                 URL: https://issues.apache.org/jira/browse/BEAM-8481
>             Project: Beam
>          Issue Type: Bug
>          Components: test-failures
>            Reporter: Ahmet Altay
>            Assignee: Valentyn Tymofieiev
>            Priority: Critical
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> [https://builds.apache.org/job/beam_PostCommit_Python37/] – this suite 
> seemingly frequently timing out. Other suites are not affected by these 
> timeouts. From the history, the issues started before Oct 10 and we cannot 
> pinpoint because history is lost.  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to