Busy upstream, it seems. 4.14 seems to have a regression regarding threadpool growing (see http://sourceforge.net/mailarchive/forum.php?thread_name=CAFUF6pBy%2Bx7A5O1cjq7JPAQDLV7hq7nKtDws5om9%3D6PPiV7gCw%40mail.gmail.com&forum_name=pyro-core) - and that's where the test suite bails for me too. If I disable that test (test_threadpool.testPoolGrowth), all checks out. So - either commit, wait for .15 or add .13 instead. The only change to the ebuild is updating homepage: remove xs4all, add http://packages.python.org/Pyro4/
Actually all versions post the 4.11 have this issue. The author says it's workarounded in 4.14: > * temporary workaround for threadpool scaling problem (lock-up): pool is > fixed at THREADPOOL_MINTHREADS threads, until the thread pool has been > redesigned to get rid of the issues.
*pyro-4.14 (01 Jun 2012) 01 Jun 2012; Amadeusz Żołnowski <aidecoe@gentoo.org> +pyro-4.14.ebuild, pyro-4.11.ebuild: Version bump wrt bug #416809. This version comes with several bug fixes and one workaround for threadpool scaling problem. I have restricted the test for this version because it fails anyway because of the latest problem which is not fully solved: FAIL: testPoolGrowth (PyroTests.test_threadpool.ThreadpoolTests)
(In reply to comment #2) Failure of 1 test is not a valid reason to restrict whole test suite.
> (In reply to comment #2) > Failure of 1 test is not a valid reason to restrict whole test suite. OK, I have removed the restriction.
