You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 13, 2025. It is now read-only.
Compilation has been running for 48+ hours, using the main-slp branch, commit 677b36f. It appears to still be running, by way of 100% CPU usage for the build process, but it has not progressed past the test_faulthandler step, so I was wondering if this kind of build time is expected when running the make command after ./configure --enable-optimizations. Thanks.
The text was updated successfully, but these errors were encountered:
Hello there.
As you may have noticed, this project is not really being actively maintained at the moment.
However, I would say that this kind of compilation time is not expected.
On the other hand, the compilation and PGO steps are all just regular standard python, running standard (non stackless) steps, ... sounds like the "test_faulthandler" unittest is simply hanging... No idea why or if it is a stackless case.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Compilation has been running for 48+ hours, using the
main-slp
branch, commit 677b36f. It appears to still be running, by way of 100% CPU usage for the build process, but it has not progressed past thetest_faulthandler
step, so I was wondering if this kind of build time is expected when running themake
command after./configure --enable-optimizations
. Thanks.The text was updated successfully, but these errors were encountered: