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

Valentyn Tymofieiev edited comment on BEAM-8481 at 12/12/19 1:18 AM:
---------------------------------------------------------------------

I can reproduce the issue locally as follows:
{noformat}
 * replace run_integration_tests.sh with a code that simply copies the SDK 
tarball into a local folder, but does not launch any pipelines
 * simplify other gradle subtask to reduce feedback loop by cutting off 
inessential operations  
 * run: $ for i in \{1..10}; do gradlew clean ; rm -rf 
sdks/python/apache_beam/portability/api/*pb2* ; gradlew :python37PostCommit; 
done
{noformat}

Half of the time the produced SDK tarball is broken.


was (Author: tvalentyn):
I can reproduce the issue locally as follows:
{noformat}
 * replace run_integration_tests.sh with a code that simply copies the SDK 
tarball into a local folder, but does not launch any pipelines
 * simplify other gradle subtask to reduce feedback loop by cutting off 
inessential operations  
 * run: $ for i in \{1..10}; do gradlew clean ; rm -rf 
apache_beam/portability/api/*pb2* ; gradlew :python37PostCommit; done
{noformat}

Half of the time the produced SDK tarball is broken.

> 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 40m
>  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