dev-python/nose tries hard to run tests faster using multiprocessing. But to be honest, this is rather fragile and I don't really feel like it's helpful. Most importantly, pypy fails all the way with it. It seems that thanks to it, the JIT warm-up problem is even worse, and the reaping is so delayed that it's easy to run out of memory. Also, it seems not really expected with our distutils-r1 parallel builds. That probably depends on the test suite, but with nosetests one it's even easier to run out of memory and the timeouts are easy to hit as well. I wonder if we shouldn't just disable that thing globally.
By "globally", do you mean adding --processes=1 to ebuilds? Or creating some wrapper function to do it? Or what?
(In reply to comment #1) > By "globally", do you mean adding --processes=1 to ebuilds? Or creating some > wrapper function to do it? Or what? I was more thinking of either modifying the package or adding some global configuration file. At least for pypy, if feasible.
commit 103f27857659150cd7b94a8d31ee8dd96b6ff5b6 Author: Justin Lecher <jlec@gentoo.org> Date: Wed Feb 3 09:34:20 2016 +0100 dev-python/nose: Drop old obsoletes: Gentoo-Bug: https://bugs.gentoo.org/show_bug.cgi?id=449748 Gentoo-Bug: https://bugs.gentoo.org/show_bug.cgi?id=449748 Gentoo-Bug: https://bugs.gentoo.org/show_bug.cgi?id=462126 Gentoo-Bug: https://bugs.gentoo.org/show_bug.cgi?id=466080 Gentoo-Bug: https://bugs.gentoo.org/show_bug.cgi?id=485022 Package-Manager: portage-2.2.27 Signed-off-by: Justin Lecher <jlec@gentoo.org> https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=103f27857659150cd7b94a8d31ee8dd96b6ff5b6
