I found this in the makefile:
# The task to run while instrumented when building the profile-opt target.
# We exclude unittests with -x that take a rediculious amount of time to
# run in the instrumented training build or do not provide much value.
PROFILE_TASK=-m test.regrtest --pgo
But whoever wrote the comment must have forgotten to actually add -x
to the command. So I added this to PKGBUILD in prepare()
:
sed -i -Ee 's|(PROFILE_TASK=-m test.regrtest --pgo)|\1 -x|' Makefile
This avoids running the tests while still building an optimized build, and gave me a functional 3.7 build in about 10 minutes.
Pinned Comments
5long commented on 2019-11-20 15:36
I'm seriously considering bumping the pkgrel for a bunch of changes:
--with-threads
is no longer recognized, which should be removed. No questions with that.Enable
--with-ensurepip
. For now, I don't see building--without-ensurepip
could yield any benefits. Theensurepip
module and.whl
s of setuptools & pip are installed anyway even when building--without-ensurepip
. It's just the bundled.whl
s might become out of date in the future, which doesn't meet Arch's "only run latest software" guideline.Running tests (either in
check()
or building with--enable-optimizations
) seems to be causing trouble for some people. Building with--enable-optimizations
claims to boost performance for 10% ~ 20% (1). Personally I don't quite care about Python's performance on my dev machine that much. Another problem is: the test suite could run for as long as 30+ minutes, which is pretty slow comparing with other AUR packages that I use. But I'm guessing that people might expect this package to be "just like python in the official repo", which is built with--enable-optimizations
enabled. So I still haven't decided on this yet.