unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Noah Lavine <noah.b.lavine@gmail.com>
Cc: 10647@debbugs.gnu.org, 10647-done@debbugs.gnu.org,
	Rob Browning <rlb@defaultvalue.org>
Subject: bug#10647: Guile 2.0.3: fails make check on s390 in threads.test
Date: Wed, 05 Sep 2012 22:23:21 +0200	[thread overview]
Message-ID: <87pq60xlqe.fsf@gnu.org> (raw)
In-Reply-To: <CA+U71=PSkMOw9OZsF3H02k5J02Zr7iB6rCjHmi0mUZyYS+S7Vw@mail.gmail.com> (Noah Lavine's message of "Tue, 4 Sep 2012 20:22:46 -0400")

Hi!

Noah Lavine <noah.b.lavine@gmail.com> skribis:

> I'm not an expert on GC, but I've seen similar issues pop up several
> times. Apparently there is at least one (and I suspect several) Guile
> tests whose outputs are nondeterministic. If so, could we make those
> tests always succeed?

Yes, almost all GC-related tests are non-deterministic.  Some are more
likely to fail on 32-bit arches, too.  I agree this can be confusing.

In the past, some of these tests were changed to throw to 'unresolved
instead of failing.  This addresses the issue by not alerting users for
non-issues.  As a side effect, we basically ignore these tests, which
isn’t good either.

So I’d try to be caution and only move from fail to unresolved those
tests, for which we routinely observe random failures.  On my laptop and
on Hydra, none of these tests fails, neither on x86_64 nor on i686, so
I’d be inclined to let them as is.

WDYT?

Thanks,
Ludo’.





      reply	other threads:[~2012-09-05 20:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-30  3:36 bug#10647: Guile 2.0.3: fails make check on s390 in threads.test Rob Browning
2012-09-03 20:52 ` Ludovic Courtès
2012-09-05  0:22   ` Noah Lavine
2012-09-05 20:23     ` Ludovic Courtès [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=87pq60xlqe.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=10647-done@debbugs.gnu.org \
    --cc=10647@debbugs.gnu.org \
    --cc=noah.b.lavine@gmail.com \
    --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).