-
-
Notifications
You must be signed in to change notification settings - Fork 31k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Race condition during installation in parallel builds #104692
Comments
jefferyto
added a commit
to jefferyto/cpython
that referenced
this issue
May 20, 2023
This ensures that commoninstall is completed before bininstall is started when parallel builds are used (make -j install), and so the python3 symlink is only installed after all standard library modules are installed.
jefferyto
added a commit
to jefferyto/cpython
that referenced
this issue
May 20, 2023
This ensures that `commoninstall` is completed before `bininstall` is started when parallel builds are used (`make -j install`), and so the `python3` symlink is only installed after all standard library modules are installed.
jefferyto
added a commit
to jefferyto/cpython
that referenced
this issue
May 20, 2023
This ensures that `commoninstall` is completed before `bininstall` is started when parallel builds are used (`make -j install`), and so the `python3` symlink is only installed after all standard library modules are installed.
ambv
pushed a commit
that referenced
this issue
Jun 7, 2023
…04693) This ensures that `commoninstall` is completed before `bininstall` is started when parallel builds are used (`make -j install`), and so the `python3` symlink is only installed after all standard library modules are installed. Co-authored-by: Zachary Ware <zachary.ware@gmail.com>
jefferyto
added a commit
to jefferyto/cpython
that referenced
this issue
Jun 7, 2023
…ininstall (pythonGH-104693) This ensures that `commoninstall` is completed before `bininstall` is started when parallel builds are used (`make -j install`), and so the `python3` symlink is only installed after all standard library modules are installed. Co-authored-by: Zachary Ware <zachary.ware@gmail.com> (cherry picked from commit 990cb36) Co-authored-by: Jeffery To <jeffery.to@gmail.com>
This was referenced Jun 7, 2023
jefferyto
added a commit
to jefferyto/cpython
that referenced
this issue
Jun 7, 2023
…ininstall (pythonGH-104693) This ensures that `commoninstall` is completed before `bininstall` is started when parallel builds are used (`make -j install`), and so the `python3` symlink is only installed after all standard library modules are installed. Co-authored-by: Zachary Ware <zachary.ware@gmail.com>. (cherry picked from commit 990cb36) Co-authored-by: Jeffery To <jeffery.to@gmail.com>
ambv
pushed a commit
that referenced
this issue
Jul 5, 2023
…all (GH-104693) (#105429) This ensures that `commoninstall` is completed before `bininstall` is started when parallel builds are used (`make -j install`), and so the `python3` symlink is only installed after all standard library modules are installed. . (cherry picked from commit 990cb36) Co-authored-by: Erlend E. Aasland <erlend.aasland@protonmail.com>
Fixes have been merged, closing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug report
When running
make -j install
, it is possible for thepython3
symlink to be installed before all standard library modules are installed. If an external program tries to run Python at this moment it can lead to an execution error.We are getting sporadic build errors at OpenWrt (openwrt/packages#19241) and believe this to be the cause, that during the build for "host" Python (Python that runs on the buildbot), another package being built tries to run a script using this Python because the
python3
symlink is in place.Your environment
Linked PRs
The text was updated successfully, but these errors were encountered: