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

Kyle Weaver commented on BEAM-8866:
-----------------------------------

This happened twice on the same PR -- Python 3.5 
portableWordCountFlinkRunnerBatch and Python 3.7 
portableWordCountSparkRunnerBatch.

The path '/tmp/py-wordcount-direct-0000x-of-0000y' is reused by multiple tests, 
so a race condition there seems a likely cause.

Also, deleting these files is a cleanup step, so it should not be a failure 
condition for the tests.

Logs:
https://builds.apache.org/job/beam_PostCommit_Python35_PR/104/console
https://builds.apache.org/job/beam_PostCommit_Python37_PR/109/console

> portableWordCount Flink/Spark - flaky post commits
> --------------------------------------------------
>
>                 Key: BEAM-8866
>                 URL: https://issues.apache.org/jira/browse/BEAM-8866
>             Project: Beam
>          Issue Type: Sub-task
>          Components: runner-flink
>            Reporter: Ahmet Altay
>            Assignee: Kyle Weaver
>            Priority: Critical
>
> Logs: 
> [https://scans.gradle.com/s/rkdiftvzvr7cy/console-log?task=:sdks:python:test-suites:portable:py36:portableWordCountFlinkRunnerStreaming]
> Error:
> ..
>   File 
> "/home/jenkins/jenkins-slave/workspace/beam_PostCommit_Python36/src/sdks/python/apache_beam/io/localfilesystem.py",
>  line 335, in delete   File 
> "/home/jenkins/jenkins-slave/workspace/beam_PostCommit_Python36/src/sdks/python/apache_beam/io/localfilesystem.py",
>  line 335, in delete     raise BeamIOError("Delete operation failed", 
> exceptions) apache_beam.io.filesystem.BeamIOError: Delete operation failed 
> with exceptions \{'/tmp/py-wordcount-direct-00001-of-00002': OSError('No 
> files found to delete under: /tmp/py-wordcount-direct-00001-of-00002',), 
> '/tmp/py-wordcount-direct-00000-of-00002': OSError('No files found to delete 
> under: /tmp/py-wordcount-direct-00000-of-00002',)} During handling of the 
> above exception, another exception occurred:
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to