unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Hans Aberg <haberg-1@telia.com>
To: Mark H Weaver <mhw@netris.org>
Cc: 10681@debbugs.gnu.org, "Ludovic Courtès" <ludo@gnu.org>
Subject: bug#10681: GNU Guile 2.0.5 released
Date: Wed, 1 Feb 2012 15:14:05 +0100	[thread overview]
Message-ID: <5ECC16F6-1210-4ABD-B379-CAC2376E646F@telia.com> (raw)
In-Reply-To: <87pqdze3c0.fsf@netris.org>

On 1 Feb 2012, at 02:42, Mark H Weaver wrote:

>> Running bytevectors.test
>> FAIL: bytevectors.test: 2.3 Operations on Bytes and Octets: bytevector-sint-ref [small] (eval)
>> FAIL: bytevectors.test: 2.3 Operations on Bytes and Octets: bytevector-sint-ref [small] (compile)
> 
> In the directory where you built using GCC-4.7.0 (SVN), can you please
> apply the following 'patch for bytevectors.test' …

This assumes that one builds from within the source directory. 

> and then, from the
> guile-2.0.5 directory, run:
> 
>  ./check-guile bytevectors.test
> 
> and show us the output?

It did not help (output below). 

Hans


$ ./check-guile bytevectors.test
Testing /usr/local/src/guile/gcc-4.7/guile-2.0.5-build/meta/guile ... bytevectors.test
with GUILE_LOAD_PATH=/usr/local/src/guile/gcc-4.7/guile-2.0.5/test-suite
Running bytevectors.test
bytevector-sint-ref [small] failure: -16 4294967280
FAIL: bytevectors.test: 2.3 Operations on Bytes and Octets: bytevector-sint-ref [small] (eval)
bytevector-sint-ref [small] failure: -16 4294967280
FAIL: bytevectors.test: 2.3 Operations on Bytes and Octets: bytevector-sint-ref [small] (compile)

Totals for this test run:
passes:                 132
failures:               2
unexpected passes:      0
expected failures:      0
unresolved test cases:  0
untested test cases:    0
unsupported test cases: 0
errors:                 0







  parent reply	other threads:[~2012-02-01 14:14 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87r4yg3l3e.fsf@gnu.org>
2012-01-31 14:21 ` bug#10681: GNU Guile 2.0.5 released Hans Aberg
2012-01-31 14:40   ` Andy Wingo
2012-01-31 15:04     ` Hans Aberg
2012-01-31 15:18   ` Ludovic Courtès
2012-01-31 16:59     ` Hans Aberg
2012-01-31 18:04   ` Mark H Weaver
2012-01-31 19:30     ` Hans Aberg
2012-01-31 19:35       ` Mark H Weaver
2012-01-31 19:41         ` Hans Aberg
2012-01-31 20:01         ` Hans Aberg
2012-01-31 22:02         ` Hans Aberg
2012-02-01  1:42           ` Mark H Weaver
2012-02-01  9:35             ` Hans Aberg
2012-02-01 14:14             ` Hans Aberg [this message]
2012-02-01  1:34         ` Hans Aberg
2012-02-01  1:49           ` Mark H Weaver
2012-02-01  9:18             ` Hans Aberg
2012-02-01 11:50               ` Andy Wingo
2012-02-01 13:36                 ` Hans Aberg
2012-02-01 14:53                   ` Andy Wingo
2012-02-01 15:08                     ` Hans Aberg
2012-07-06 18:23                       ` Andy Wingo
2012-07-07 12:03                         ` bug#10681: GNU Guile 2.0.6 released Hans Aberg

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=5ECC16F6-1210-4ABD-B379-CAC2376E646F@telia.com \
    --to=haberg-1@telia.com \
    --cc=10681@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=mhw@netris.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).