unarchive 647296 reopen 647296 thanks On Fri, Nov 04, 2011 at 08:00:48AM -0700, Daniel Schepler wrote: > >It was my local rebuild of 3.0.0-2-amd64 version 3.0.0-5. But I don't know if >it's very version dependent: the last version of ruby1.9.1 this machine has >built successfuly was 1.9.2.290-2 on Jul 27.
I'm now seeing exactly this too on a variety of armhf machines, when trying to verify that #652674 is fixed. I'm seeing this on abel (armhf porter box) right now. I can't see any ruby processes using CPU at all, suggesting a locking bug or something(?). Is there in particular I could look at to help here? Looking for the test code to debug what it's trying to do, I can't find anything intelligible, which isn't helping. :-( -- Steve McIntyre, Cambridge, UK. st...@einval.com "C++ ate my sanity" -- Jon Rabone -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
