Re: debian packages of guile 1.9/2.0

Re: debian packages of guile 1.9/2.0

[Neil Jerram]

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.

Is it with the plain 1.9.0 release tarball, or with Debian patches
too?  Also how did you configure?

>  It looks like someone else
> had a similar problem:
>
>   http://www.mail-archive.com/bug-guile@gnu.org/msg04426.html

Yes, but with no followup.

> I'll send this to bug-guile if it's not already under consideration.

I've cc'ed this email there.

Regards,
        Neil

Re: debian packages of guile 1.9/2.0

[Neil Jerram]

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