Hi, Nathan Gray <[email protected]> writes: > In another terminal I investigated a little bit. It looks like > 'darcs unpull' is hanging: > > $ date > Tue Dec 29 16:29:33 EST 2009 > > $ ps ax|grep darcs > 5311 pts/0 S+ 0:17 darcs-benchmark /home/kolibrie/bin/darcs-2.3.1 > /home/kolibrie/bin/darcs > 6136 pts/0 Sl+ 0:21 /home/kolibrie/bin/darcs-2.3.1 unpull --last 1000 > --all +RTS -sdarcs-stats -RTS > > $ uptime > 16:29:31 up 1:05, 3 users, load average: 0.10, 0.32, 0.47 I have seen this happen (actually, it happens on buildbot as well, and it doesn't happen on my laptop...), too. The question is what's going wrong... On the buildbot, I haven't noticed any hanging darcs processes. I am starting to suspect, that darcs is waiting for some user input in that case. It could be the "this will make unrevert impossible" one, but I don't see anything in the benchmark code that could produce one and there is none in the tarballs. Also, it should be reproducible that way.
> Any ideas what I should do, besides kill it? If you could find out what that hanging darcs process is doing (strace -p is your friend), that'd be great. Also, running that command manually could help to find out: go to _playground/repo and run darcs-2.3.1 unpull --last 1000 --all. Thanks, Petr. _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
