[
https://issues.apache.org/jira/browse/BEAM-8196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16927886#comment-16927886
]
Robert Bradshaw commented on BEAM-8196:
---------------------------------------
Yes, I think we could make this an error if we're sure end users won't have
issues (i.e. all the files are already there with the right timestamps).
> 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: 0.5h
> 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.2#803003)
