From: Eric Wong <email@example.com>
Subject: Re: raindrops tests fail on smp, fork is to blame
Date: Fri, 22 Jun 2012 15:29:20 -0700 [thread overview]
Message-ID: <20120622222920.GA32552@dcvr.yhbt.net> (raw)
Hleb Valoshka <firstname.lastname@example.org> wrote:
> Raindrops build hangs on debian's build servers, but not on my local
> box. This occurs when tests are run under ruby1.9.1. You can see
> example of build log in . It took a lot of time to understand that
> the main difference between build and my box is number of CPUs:
> debian's servers are smp, my kvm box had only 1 cpu.
> Today I decided to start kvm with option -smp 2, and voila! build
> hung. The more tests with fork() you have the higher probability build
> will hang. When all tests are enabled, the probability of hang is
> about 100% when tests are run by gem2deb (it loads all test files
> simultaneously) and about 5-10% with "make test". When test_concurrect
> from test_middleware.rb and test_incr_shared, test_incr_decr and
> test_evaporate_with_fork from test_raindrops.rb are disabled build
> runs without hangs.
> Any ideas?
This is only on GNU/kFreeBSD, right?
I managed to reproduce this on my older Debian GNU/kFreeBSD 6.0 KVM
I suspect it's a bad interaction with the internal timer thread of Ruby
1.9 and fork(). Probably some mutex is held when the fork() happens
and attempting to acquire it in the child process causes a deadlock.
Even without loading raindrops, the following code locks up for
me with ruby1.9.1 22.214.171.124-2 on my Debian GNU/kFreeBSD 6.0 instance:
pid = fork do
1 + 1
Can you try it on 1.9.3-p194 on your newer wheezy/sid install?
I think some libc folks will need to be roped into this fix this.
next prev parent reply other threads:[~2012-06-22 22:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 21:06 raindrops tests fail on smp, fork is to blame Hleb Valoshka
2012-06-22 22:29 ` Eric Wong [this message]
2012-06-23 11:59 ` Hleb Valoshka
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
List information: https://yhbt.net/raindrops/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).