https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257353
Naram Qashat <cyberb...@cyberbotx.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |cyberb...@cyberbotx.com
--- Comment #6 from Naram Qashat <cyberb...@cyberbotx.com> ---
So I know this bug is for lang/python38 specifically, but I wanted to bring up
that I've been having this problem repeatedly when building either
lang/python39 or lang/python310 in a poudriere aarch64 jail under an amd64
machine. It happens more than it doesn't, and my recent move from the default
python of 3.9 to using 3.10 was because of this problem, but now 3.10 is doing
the same thing.
To answer koobs' questions for my case specifically:
uname -a:
FreeBSD kirby.cyberbotx.com 13.1-RELEASE-p2 FreeBSD 13.1-RELEASE-p2
releng/13.1-n250158-752f813d6cc GENERIC amd64
Host is amd64 13.1-RELEASE-p2, Target is aarch64 13.1-RELEASE-p2
Latest full build log with the failure:
https://poudriere.cyberbotx.com:8766/data/local_aarch64-default/2022-12-11_23h33m03s/logs/errors/python310-3.10.9_1.log
(Just to note for the above, sometimes when the BadProcessPool happens, instead
of proceeding, it just gets completely stuck and if I don't kill poudriere,
it'll eventually kill the build was a runaway process.)
As mentioned above, I've had this happen repeatedly for many of the
lang/python<ver> ports. I don't know what allows it to actually complete
successfully or not.
--
You are receiving this mail because:
You are on the CC list for the bug.
