[
https://issues.apache.org/jira/browse/BEAM-8481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16987352#comment-16987352
]
Valentyn Tymofieiev edited comment on BEAM-8481 at 12/3/19 11:24 PM:
---------------------------------------------------------------------
[~udim], see my previous message, the error started happening earlier than
#9572. After reviewing [1], I think https://github.com/apache/beam/pull/9277 is
the culprit. https://github.com/apache/beam/pull/10257 is out to restore the
timeout.
[1]
https://github.com/apache/beam/pulls?q=is%3Apr%20is%3Aclosed+merged%3A2019-08-07..2019-08-09+base%3Amaster+sort%3Aupdated-desc.
was (Author: tvalentyn):
[~udim], see above the error started happening earlier. After reviewing [1], I
think https://github.com/apache/beam/pull/9277 is the culprit.
https://github.com/apache/beam/pull/10257 is out to restore the timeout.
[1]
https://github.com/apache/beam/pulls?q=is%3Apr%20is%3Aclosed+merged%3A2019-08-07..2019-08-09+base%3Amaster+sort%3Aupdated-desc.
> Python 3.7 Postcommit test -- frequent timeouts
> -----------------------------------------------
>
> Key: BEAM-8481
> URL: https://issues.apache.org/jira/browse/BEAM-8481
> Project: Beam
> Issue Type: Bug
> Components: test-failures
> Reporter: Ahmet Altay
> Assignee: Valentyn Tymofieiev
> Priority: Critical
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> [https://builds.apache.org/job/beam_PostCommit_Python37/] – this suite
> seemingly frequently timing out. Other suites are not affected by these
> timeouts. From the history, the issues started before Oct 10 and we cannot
> pinpoint because history is lost.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
