The parallel doctester doesn't error out in some instances where resource limits are hit, and sometimes just hangs at the end waiting for the process that failed to spawn. The fact that it works when you reduce the number of parallel processes strongly suggests that this is what you are hitting.
On Saturday, March 7, 2015 at 1:52:05 PM UTC+1, tha...@debian.org wrote: > > Hi, > > I am experimenting with building Sage in a Debian unstable chroot and > have a hard time figuring out why parallel doctesting does not work. > I wonder if it has something to do with the chroot. I already run into > the problem that /dev/shm was not user-writable and fixed that. The > script from [1] now runs without error so /dev/pts should also be in > place. > > When I run the test suite in parallel it ends up in the "while True" > loop of parallel_dispatch() in src/sage/doctest/forker.py as intended, > however top shows that no processes are using any CPU. > > When I run > ./sage -tp 1 --long --all > parallel_dispatch() is also used but now everything works. > > Any ideas what about the chroot could cause this or how I can find out > more? Parallel building works in the chroot by the way. > > Best, > Tobias > > [1] http://trac.sagemath.org/ticket/5965 > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
