GNU bug report logs - #10647
Guile 2.0.3: fails make check on s390 in threads.test

Previous Next

Full log

Message #19 received at 10647 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: Noah Lavine <noah.b.lavine <at> gmail.com>
Cc: 10647 <at> debbugs.gnu.org, 10647-done <at> debbugs.gnu.org,
	Rob Browning <rlb <at> defaultvalue.org>
Subject: Re: bug#10647: Guile 2.0.3: fails make check on s390 in threads.test
Date: Wed, 05 Sep 2012 22:23:21 +0200

Hi!

Noah Lavine <noah.b.lavine <at> 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’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.