[
https://issues.apache.org/jira/browse/BEAM-8196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16927851#comment-16927851
]
Ahmet Altay commented on BEAM-8196:
-----------------------------------
Great, thank you [~udim]. That sounds like a promising start.
[~alanmyrvold][~yifanzou] -- Question, for jobs that run on Dataflow could we
introduce a timeout parameter to convert these jenkins level job timeouts to
dataflow level job timeouts? Would that be a bad/good idea? Increase flakiness?
> 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)
