[ 
https://issues.apache.org/jira/browse/BEAM-8481?focusedWorklogId=361259&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-361259
 ]

ASF GitHub Bot logged work on BEAM-8481:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 18/Dec/19 01:53
            Start Date: 18/Dec/19 01:53
    Worklog Time Spent: 10m 
      Work Description: tvalentyn commented on issue #10378: [BEAM-8481] Fix a 
race condition in proto stubs generation.
URL: https://github.com/apache/beam/pull/10378#issuecomment-566830870
 
 
   New errors: https://issues.apache.org/jira/browse/BEAM-8988. 
   Overall, postcommits are running and no longer timing out. I suggest we 
merge this PR since it will help reduce flakiness, which in turn will help 
verify fixes for BEAM-8988. @udim could you please review and/or merge if that 
sounds good to you?
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 361259)
    Time Spent: 4h 10m  (was: 4h)

> 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: 4h 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)

Reply via email to