From: Hleb Valoshka <375gnu@gmail.com>
To: raindrops@librelist.org
Subject: Re: raindrops tests fail on smp, fork is to blame
Date: Sat, 23 Jun 2012 14:59:30 +0300 [thread overview]
Message-ID: <CAAB-Kc=5jU_TunhmpqXZdUjr+4y1vYwv3vCgJNjLMP=-3Myo2A@mail.gmail.com> (raw)
In-Reply-To: 20120622222920.GA32552@dcvr.yhbt.net
On 6/23/12, Eric Wong <normalperson@yhbt.net> wrote:
> This is only on GNU/kFreeBSD, right?
Yes, only kFreeBSD, I didn't notice that I forgot to mention this fact.
> Can you try it on 1.9.3-p194 on your newer wheezy/sid install?
It locks always. Sometimes after 2 first forks, onсe just after the first fork.
> I think some libc folks will need to be roped into this fix this.
Okay, I'll send your code to gnu/kfreebsd guys to use it as test case.
prev parent reply other threads:[~2012-06-23 11:59 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
2012-06-23 11:59 ` Hleb Valoshka [this message]
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://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=5jU_TunhmpqXZdUjr+4y1vYwv3vCgJNjLMP=-3Myo2A@mail.gmail.com' \
--to=375gnu@gmail.com \
--cc=raindrops@librelist.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://yhbt.net/raindrops.git/
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).