raindrops RubyGem user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Hleb Valoshka <375gnu@gmail.com>
To: raindrops@librelist.org
Subject: raindrops tests fail on smp, fork is to blame
Date: Sat, 23 Jun 2012 00:06:30 +0300	[thread overview]
Message-ID: <CAAB-Kc=wfr0EQJ7h=YJ1J5NmAogEYbXmzy9f9Q6H21+-mntJ9w@mail.gmail.com> (raw)
In-Reply-To: <CAAB-Kc=wfr0EQJ7h=YJ1J5NmAogEYbXmzy9f9Q6H21+-mntJ9w@mail.gmail.com>


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 [0]. 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?

[0] https://buildd.debian.org/status/fetch.php?pkg=ruby-raindrops&arch=kfreebsd-amd64&ver=0.9.0-1&stamp=1340389966

       reply	other threads:[~2012-06-22 21:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-22 21:06 Hleb Valoshka [this message]
2012-06-22 22:29 ` raindrops tests fail on smp, fork is to blame Eric Wong
2012-06-23 11:59   ` Hleb Valoshka

Reply instructions:

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: http://yhbt.net/raindrops/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAAB-Kc=wfr0EQJ7h=YJ1J5NmAogEYbXmzy9f9Q6H21+-mntJ9w@mail.gmail.com' \
    --to=375gnu@gmail.com \
    --cc=raindrops@librelist.org \


* 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).