emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#10647: closed (Guile 2.0.3: fails make check on s3


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#10647: closed (Guile 2.0.3: fails make check on s390 in threads.test)
Date: Mon, 03 Sep 2012 20:55:02 +0000

Your message dated Mon, 03 Sep 2012 22:52:24 +0200
with message-id <address@hidden>
and subject line Re: bug#10647: Guile 2.0.3: fails make check on s390 in 
threads.test
has caused the debbugs.gnu.org bug report #10647,
regarding Guile 2.0.3: fails make check on s390 in threads.test
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
10647: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=10647
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: Guile 2.0.3: fails make check on s390 in threads.test Date: Sun, 29 Jan 2012 21:36:28 -0600 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux)
Package: Guile
Version: 2.0.3

Make check fails on the s390x architecture:

  FAIL: threads.test: mutex-ownership: mutex with owner not retained (bug 
#27450)

You can see the full build log here:

  
https://buildd.debian.org/status/fetch.php?pkg=guile-2.0&arch=s390&ver=2.0.3%2B1-3&stamp=1327882482

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4



--- End Message ---
--- Begin Message --- Subject: Re: bug#10647: Guile 2.0.3: fails make check on s390 in threads.test Date: Mon, 03 Sep 2012 22:52:24 +0200 User-agent: Gnus/5.130005 (Ma Gnus v0.5) Emacs/24.2 (gnu/linux)
Hi Rob,

Rob Browning <address@hidden> skribis:

>   FAIL: threads.test: mutex-ownership: mutex with owner not retained (bug 
> #27450)

This one is harmless, and can be ignored.  It’s a consequence of using a
conservative GC, which is non-deterministic.

So closing this bug (and looking at the others, yes! ;-)).

Thanks,
Ludo’.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]