unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
To: Rob Browning <rlb@defaultvalue.org>
Cc: "Guile Bugs" <bug-guile@gnu.org>, "Ludovic Courtès" <ludo@gnu.org>
Subject: Re: debian packages of guile 1.9/2.0
Date: Sun, 21 Jun 2009 18:28:08 +0100	[thread overview]
Message-ID: <87k535pkd3.fsf@arudy.ossau.uklinux.net> (raw)
In-Reply-To: <8763epbx0k.fsf@arudy.ossau.uklinux.net> (Neil Jerram's message of "Sun\, 21 Jun 2009 13\:18\:35 +0100")

Neil Jerram <neil@ossau.uklinux.net> writes:

> Rob Browning <rlb@defaultvalue.org> writes:
>
>> It builds, but it looks like there's a make check error:
>>
>>   Running threads.test
>>   FAIL: threads.test: lock-mutex: timed locking succeeds if mutex
>>   unlocked within timeout
>>   Running time.test
>>
>> This is on fairly recent debian unstable.
>
> I'll look into this.

Two thoughts.

1. Is it just that the main thread takes longer than 1 second to
unlock the mutex?  Does the test pass reliably if you increase the 2
in `(+ (current-time) 2)' to, say 5 or 10?

Note that you can run just threads.test by:

$ meta/uninstalled-env meta/guile test-suite/tests/threads.test

2. Is it something to do with specifying or converting time in the
wrong way?  (Time zone issue? - could conceivably work better in
Europe (where most of the core developers currently are) than in US?)

I guess (1) is more likely, so I'll investigate (2) in more detail if
(1) doesn't help.

Regards,
        Neil




      reply	other threads:[~2009-06-21 17:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m3y6s7bvw7.fsf@pobox.com>
     [not found] ` <873aa4c0gb.fsf@raven.defaultvalue.org>
     [not found]   ` <87ab42ydzx.fsf@raven.defaultvalue.org>
     [not found]     ` <87tz2a7a2d.fsf@raven.defaultvalue.org>
2009-06-21 12:18       ` debian packages of guile 1.9/2.0 Neil Jerram
2009-06-21 17:28         ` Neil Jerram [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=87k535pkd3.fsf@arudy.ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --cc=bug-guile@gnu.org \
    --cc=ludo@gnu.org \
    --cc=rlb@defaultvalue.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).