[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=16927801#comment-16927801 ] 

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

No idea why this happens. There isn't an easy way to tell what's going on.
Increasing the timeout wouldn't help as the running time seems pretty stable at around 60-65m: https://builds.apache.org/job/beam_PostCommit_Python35/buildTimeTrend

Another timeout:
https://builds.apache.org/job/beam_PostCommit_Python37/lastCompletedBuild/console


> 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
>
> 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.2#803003)