[jira] [Commented] (BEAM-8196) Python 3.5 post commit timed out at 100 minutes

["Udi Meiri (Jira)" <ji...@apache.org>]

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

Udi Meiri commented on BEAM-8196:
---------------------------------

This is still happening, very frequently now for 3.7 postcommits.
I investigated 6 semmingly long-running jobs on the apache-beam-testing project, they all were running "Apache Beam Python 3.7 SDK 2.17.0.dev" and all were showing the
"ModuleNotFoundError: No module named 'endpoints_pb2'".
One of these is still running after 16 hours. The rest failed after 1-2 hours. Perhaps the 16 hour one did not abort because it is a streaming job?


> Python 3.5 post commit timed out at 100 minutes
> -----------------------------------------------
>
>                 Key: BEAM-8196
>                 URL: https://issues.apache.org/jira/browse/BEAM-8196
>             Project: Beam
>          Issue Type: Sub-task
>          Components: sdk-py-core
>            Reporter: Ahmet Altay
>            Assignee: Udi Meiri
>            Priority: Critical
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> https://builds.apache.org/job/beam_PostCommit_Python35/435/
> This post commit took 100 minutes and timedout. Should we increase the timeout? We can also look into why this postcommit was slow. A later post commit (https://builds.apache.org/job/beam_PostCommit_Python35/437/) completed in 66 minutes.



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