My favorites | Sign in
Project Home Downloads Issues
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 60: Timeout::timeout failing with Kernel#exec on Ubuntu Lucid when all cores are busy
1 person starred this issue and may be notified of changes. Back to list
Status:  New
Owner:  ----


Sign in to add a comment
 
Reported by jamesmea...@gmail.com, Jan 27, 2011
As described in this Puppet thread [1] :-

1. Ensure all but one core is busy (e.g. by running "openssl speed >/dev/null &"
2. Run the following Ruby script :-

    %x{/usr/bin/touch /tmp/7777}
    puts "executed without timeout ok"

    puts "executing with timeout"

    require 'timeout'

    status = Timeout::timeout(5) {
           %x{/usr/bin/touch /tmp/7777}
    }

    puts "executed with timeout ok"

The expected output is :-

    executed without timeout ok
    executing with timeout
    executed with timeout ok

But I see this :-

    executed without timeout ok
    executing with timeout
    /usr/lib/ruby/1.8/timeout.rb:60: execution expired (Timeout::Error)
            from /root/tickle_ruby.rb:11

I'm using Ruby 1.8.7 (2010-04-19 patchlevel 253 [x86_64-linux], MBARI 0x6770, Ruby Enterprise Edition 2010.02 on Ubuntu 10.04 LTS 64-bit Server Edition (2.6.32.24-server #39-Ubuntu x86_64).  

It looks like the issue described on the puppet mailing list was on MRI Ruby, but I do not see the problem on MRI Ruby 1.8.7 (2010-01-10 patchlevel 249) [x86_64-linux], I only see it on REE. The puppet issue seems to be related to this MRI Ruby bug report [2] - I wonder if the related fixes have not been applied to REE?

[1] http://www.mail-archive.com/puppet-users@googlegroups.com/msg09156.html
[2] http://redmine.ruby-lang.org/issues/show/2739
Sign in to add a comment

Powered by Google Project Hosting