nobu / ruby-lang.org wrote:
> Is it an issue of the test code?
> 
> http://c5664.rubyci.org/~chkbuild/ruby-trunk/log/20140125T233302Z.log.html.gz

Odd, I did not get this:

 10) Error:
TestProcess#test_deadlock_by_signal_at_forking:
Errno::EINTR: Interrupted system call - /home/chkbuild/build/20140125T233302Z/ruby/ruby
    /home/chkbuild/build/20140125T233302Z/ruby/test/ruby/test_process.rb:1875:in `popen'
    /home/chkbuild/build/20140125T233302Z/ruby/test/ruby/test_process.rb:1875:in `block in test_deadlock_by_signal_at_forking'
    /home/chkbuild/build/20140125T233302Z/ruby/test/ruby/test_process.rb:1873:in `times'
    /home/chkbuild/build/20140125T233302Z/ruby/test/ruby/test_process.rb:1873:in `test_deadlock_by_signal_at_forking'

Instead, I got this (with TESTS=-j32):

/home/ew/ruby/test/ruby/test_process.rb:15:in `waitall': SIGTERM (SignalException)
        /home/ew/ruby/test/ruby/test_process.rb:15:in `teardown'
        /home/ew/ruby/lib/minitest/unit.rb:1280:in `block in run'

I don't think I was able to reproduce it on a single-threaded test-all.