On 17/02/10 at 17:45 -0000, Nigel Kersten wrote: > Sorry, I should have made this clearer. > > I work with Joel and Andrew, and am responsible for the Puppet > infrastructure here. > > I spent a while debugging what was causing Facter and/or Puppet to hang, > and it all came down to the calls being wrapped in Timeout. > > I did reproduce this on Debian Testing under VMware, but it wasn't > *quite* as reproducible as it appears to be under Lucid for me, it would > fail one in every few runs rather than absolutely every run when other > cores were busy. > > How many cores were on the machine you tried to reproduce on Lucas?
First 2, then 8. On the 8 cores one, I tried, using ruby1.8 from Debian unstable: - with libc from Debian unstable (2.10) - with libc from Debian experimental (2.11) I could not reproduce the problem in any case, unfortunately. (I'm running the script in a bash while loop.) I don't have any Ubuntu images I could deploy on this machine, and I also have a lot of other work to do tonight (CET, i.e now), so I won't be able to spend a lot more time on this before tomorrow. Are you able to reproduce it in a stock Ubuntu environment, or is it a Google-specific one? Note that the Timeout module is pure ruby, so it might be easy to reduce your test case a bit more. Thanks a lot for investigating this issue! -- | Lucas Nussbaum | [email protected] http://www.lucas-nussbaum.net/ | | jabber: [email protected] GPG: 1024D/023B3F4F | -- building ruby1.8 with pthread support causes puppet hangs https://bugs.launchpad.net/bugs/520715 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
