From: Kevin Ryde <user42@zip.com.au>
To: hkBst@gentoo.org
Cc: bug-guile@gnu.org
Subject: Re: sleep 999 after tests
Date: Sun, 19 Aug 2007 10:50:46 +1000 [thread overview]
Message-ID: <87eji0pct5.fsf@zip.com.au> (raw)
In-Reply-To: <46C55859.5020108@gentoo.org> (Marijn Schouten's message of "Fri, 17 Aug 2007 10:12:09 +0200")
"Marijn Schouten (hkBst)" <hkBst@gentoo.org> writes:
>
> This test depends on networking being enabled.
Does it? It's a pipe, not a socket.
> So how about making it 30 seconds?
No, but something that made the two processes watch more closely what
each other is doing would be fine. (I suppose the child process ought
to be killed+waited explicitly too.)
As I said though, if it's blocking for 999 then you're looking at a bug,
maybe in guile, maybe in the test.
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
prev parent reply other threads:[~2007-08-19 0:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-25 14:59 sleep 999 after tests Marijn Schouten
2007-08-16 23:11 ` Kevin Ryde
2007-08-17 8:12 ` Marijn Schouten (hkBst)
2007-08-17 13:19 ` Ludovic Courtès
2007-08-17 13:25 ` Marijn Schouten (hkBst)
2007-08-19 0:50 ` Kevin Ryde [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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eji0pct5.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=bug-guile@gnu.org \
--cc=hkBst@gentoo.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.
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).