You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Ahmet Altay (Jira)" <ji...@apache.org> on 2019/09/10 18:46:00 UTC

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

     [ https://issues.apache.org/jira/browse/BEAM-8196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ahmet Altay updated BEAM-8196:
------------------------------
    Status: Open  (was: Triage Needed)

> 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)