You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/01/08 19:29:00 UTC

[jira] [Work logged] (BEAM-8481) Python 3.7 Postcommit test -- frequent timeouts

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

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

                Author: ASF GitHub Bot
            Created on: 08/Jan/20 19:28
            Start Date: 08/Jan/20 19:28
    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-572220095
 
 
   Looked at this together with @ibzib. Portable postcommit errors are caused by this PR. Since this PR switches from installing Python SDK in developer mode to installing the SDK from a tarball, it changes the path on Jenkins workers where the SDK sources will be located after the installation. In particular, after installing the SDK from a tarball into a virtual environment, the SDK source files will be located in a location like `$path_to_virtual_env/lib/python2.7/site-packages/apache_beam/`. 
   It appears that the default path for job service jar is defined by the location of SDK sources: https://github.com/apache/beam/blob/7346cf201e847fc7596389ff8406f8352859495e/sdks/python/apache_beam/utils/subprocess_server.py#L162. Therefore with this PR, Portable Flink Runner tests look for flink-job-server.jar in a different location and cannot find it.
   
   The error can be reproed via: gradlew :sdks:python:test-suites:portable:py37:postCommitPy37
 
----------------------------------------------------------------
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:
users@infra.apache.org


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

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

> 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 20m
>  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)