[
https://issues.apache.org/jira/browse/BEAM-8194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17121897#comment-17121897
]
Kenneth Knowles commented on BEAM-8194:
---------------------------------------
This issue is assigned but has not received an update in 30 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> virtualSetupEnv task is flaky
> -----------------------------
>
> Key: BEAM-8194
> URL: https://issues.apache.org/jira/browse/BEAM-8194
> Project: Beam
> Issue Type: Sub-task
> Components: sdk-py-core
> Reporter: Ahmet Altay
> Assignee: Valentyn Tymofieiev
> Priority: P1
> Labels: stale-assigned
>
> PyPI sometimes fails when it cannot find dependencies. This happens even when
> dependencies exist.
> Example: https://builds.apache.org/job/beam_PostCommit_Python2/433/consoleFull
> Log:
> 05:00:54 Collecting filelock<4,>=3.0.0 (from tox==3.11.1)
> 05:00:54 ERROR: Could not find a version that satisfies the requirement
> filelock<4,>=3.0.0 (from tox==3.11.1) (from versions: none)
> 05:00:54 ERROR: No matching distribution found for filelock<4,>=3.0.0 (from
> tox==3.11.1)
> 05:00:57
> 05:00:57 > Task :sdks:python:setupVirtualenv FAILED
> There was a previous attempt to fix this
> (https://github.com/apache/beam/pull/7519/files) by adding `--retries 10` to
> the pip command. However, this only works with connections
> (https://pip.pypa.io/en/stable/reference/pip/#cmdoption-retries) and I am
> guessing that when pip decides that a dependency does not exist it requires
> more than a network retry.
> We could try a gradle task level retry, or wrap the virtualenv creation in a
> shell script and try do a retry on that.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
