You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Udi Meiri (Jira)" <ji...@apache.org> on 2019/09/12 17:51:00 UTC
[jira] [Comment Edited] (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:comment-tabpanel&focusedCommentId=16928752#comment-16928752 ]
Udi Meiri edited comment on BEAM-8196 at 9/12/19 5:50 PM:
----------------------------------------------------------
#9547 was merged ~18 hours ago, but this postcommit timed out about 4 hours ago:
https://builds.apache.org/job/beam_PostCommit_Python37/lastCompletedBuild/console
edit: it seems that all (at least 2) of these tests failed due to endpoints_pb2 import failure.
was (Author: udim):
#9547 was merged ~18 hours ago, but this postcommit timed out about 4 hours ago:
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
> 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.2#803003)