unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Matt Wette <matt.wette@gmail.com>
To: guile-devel@gnu.org
Cc: Andy Wingo <wingo@pobox.com>
Subject: Re: GNU Guile 2.1.5 released (beta)
Date: Sun, 11 Dec 2016 07:17:25 -0800	[thread overview]
Message-ID: <F0DE42D4-50AC-4D2A-AA98-AFEC0230F751@gmail.com> (raw)
In-Reply-To: <B3C8DE19-0B70-4D93-8A1B-6D740DA07167@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1255 bytes --]


> On Dec 9, 2016, at 7:28 AM, Matt Wette <matt.wette@gmail.com> wrote:
> 
> 
>> On Dec 7, 2016, at 11:55 AM, Andy Wingo <wingo@pobox.com> wrote:
>> 
>> We are pleased to announce GNU Guile release 2.1.5.
>> 
>> Guile 2.1.5 is the fifth pre-release in what will eventually become the
>> 2.2 release series.  We encourage you to test this release and provide
>> feedback to guile-devel@gnu.org.
> 
> I am building on my Mac running macOS 10.12.1, aka Sierra.  I will post my patches when I get through “make check”.  

Now getting through make check, but this, from threads.test, fails:

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

        (pass-if "mutex with owner not retained (bug #27450)"
          (let ((g (make-guardian)))
            (g (let ((m (make-mutex))) (lock-mutex m) m))

            ;; Avoid false references to M on the stack.
            (clear-stale-stack-references)

            (gc) (gc)
            (let ((m (g)))
              (and (mutex? m)
                   (eq? (mutex-owner m) (current-thread)))))))

debbugs.gnu.org says 27450 does not exist.  My guess is the mutex m should be preserved by clear-stale-stack-references + gc but it is not.

Matt


[-- Attachment #2: Type: text/html, Size: 5841 bytes --]

  parent reply	other threads:[~2016-12-11 15:17 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-07 19:55 GNU Guile 2.1.5 released (beta) Andy Wingo
2016-12-09 15:28 ` Matt Wette
2016-12-09 17:25   ` Christopher Allan Webber
2016-12-10 13:16   ` Matt Wette
2016-12-11 14:52     ` Matt Wette
2016-12-11 15:42     ` Matt Wette
2017-01-08 22:50       ` Andy Wingo
2016-12-11 15:17   ` Matt Wette [this message]
2016-12-12 13:45     ` Matt Wette
2016-12-12 20:46       ` Matt Wette
2016-12-13  1:24         ` dsmich
2016-12-13 21:26           ` Freja Nordsiek
2016-12-16 13:50             ` Matt Wette
2016-12-16 14:05               ` Matt Wette
2016-12-17  2:03                 ` Christopher Allan Webber
2016-12-17  3:07                   ` Matt Wette
2016-12-11 20:35 ` Matt Wette
2016-12-12  1:25   ` Matt Wette
2016-12-12 11:14     ` tomas
2017-01-08 22:54     ` Andy Wingo
2017-01-09  0:13       ` Matt Wette
2016-12-20 15:00 ` Matt Wette
2016-12-20 22:58   ` Matt Wette
2017-01-08 23:01     ` Andy Wingo
2017-01-08 23:28       ` Matt Wette
     [not found] <mailman.109.1481389218.15985.guile-devel@gnu.org>
2016-12-10 17:11 ` Daniel Llorens
2016-12-11  0:42   ` Matt Wette
2016-12-29 19:38     ` Matt Wette

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=F0DE42D4-50AC-4D2A-AA98-AFEC0230F751@gmail.com \
    --to=matt.wette@gmail.com \
    --cc=guile-devel@gnu.org \
    --cc=wingo@pobox.com \
    /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).