[
https://issues.apache.org/jira/browse/BEAM-8481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16988369#comment-16988369
]
Udi Meiri commented on BEAM-8481:
---------------------------------
Following up on a conversion with Valentyn.
Assuming that setup.py sdist creates the same tarball regardless of Python
version (i.e. futurize is called and converts the aforementioned relative
import of endpoints_pb2 to absolute),
the underlying issue seems to be a concurrency issue with running setup.py.
Assuming that nothing else but setup.py generates endpoints_pb2, perhaps we
should prevent setup.py from running in parallel with itself.
What I'm proposing is for setup.py to create and acquire a file lock (in the
CWD for instance), to prevent multiple instances from stepping over each other.
See also this bug which clearly spells out that setuptools is not thread or
multi-process safe: https://github.com/pypa/setuptools/issues/1222
> 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)
