unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Chris Marusich <cmmarusich@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Adding a TOR system test - confusing results
Date: Thu, 26 Jul 2018 15:36:40 +0200	[thread overview]
Message-ID: <87effqyv87.fsf@gnu.org> (raw)
In-Reply-To: <87wotltjig.fsf@gmail.com> (Chris Marusich's message of "Mon, 23 Jul 2018 20:11:51 -0700")

Hello,

Chris Marusich <cmmarusich@gmail.com> skribis:

> Why does it pass?  The (sleep 999999) form appears to be totally
> ignored, and I don't understand why.  It's concerning to me that I can't
> understand how the code is being executed.  I expected the test to hang.

According to the manual (info "(guile) Signals"):

--8<---------------cut here---------------start------------->8---
 -- Scheme Procedure: sleep secs
 -- Scheme Procedure: usleep usecs
 -- C Function: scm_sleep (secs)
 -- C Function: scm_usleep (usecs)
     Wait the given period SECS seconds or USECS microseconds (both
     integers).  If a signal arrives the wait stops and the return value
     is the time remaining, in seconds or microseconds respectively.  If
     the period elapses with no signal the return is zero.
--8<---------------cut here---------------end--------------->8---

So I suspect that the marionette process got a signal, and thus ‘sleep’
returned quickly.  Could you print its return value?

HTH,
Ludo’.

  reply	other threads:[~2018-07-26 13:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-23  0:14 Adding a TOR system test - confusing results Chris Marusich
2018-07-23  9:01 ` Ludovic Courtès
2018-07-24  3:11   ` Chris Marusich
2018-07-26 13:36     ` Ludovic Courtès [this message]
2018-07-27  5:13       ` Chris Marusich
2018-07-27  8:19         ` Chris Marusich
2018-07-27  8:41         ` Ludovic Courtès
2018-07-27  9:58           ` Chris Marusich

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://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87effqyv87.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=cmmarusich@gmail.com \
    --cc=guix-devel@gnu.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://git.savannah.gnu.org/cgit/guix.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).