public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/48243] Several libgo tests fail on Solaris 10/SPARC
Date: Thu, 16 Feb 2012 20:00:00 -0000 [thread overview]
Message-ID: <bug-48243-4-sAmuo8AcW5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48243-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48243
--- Comment #2 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> 2012-02-16 19:21:17 UTC ---
> --- Comment #1 from Ian Lance Taylor <ian at airs dot com> 2012-02-14 19:44:21 UTC ---
> I think these are all fixed now.
Right. The only failures left are crypto/rand due to the 1040 byte read
limit on /dev/urandom, and several others which seem to be races with
testdata symlinks:
=== libgo tests ===
Running target unix
FAIL: compress/flate
FAIL: crypto/rand
FAIL: image/jpeg
=== libgo Summary for unix ===
# of expected passes 120
# of unexpected failures 3
Running target unix/-m64
FAIL: compress/flate
FAIL: compress/lzw
FAIL: compress/zlib
FAIL: crypto/rand
FAIL: image/jpeg
=== libgo Summary for unix/-m64 ===
# of expected passes 118
# of unexpected failures 5
e.g.
ln: creating symbolic link `../testdata/testdata': File exists
PASS
PASS: compress/bzip2
ln: creating symbolic link `../testdata/testdata': File exists
--- FAIL: flate.TestDeflateInflateString (0.08 seconds)
???:1: open ../testdata/e.txt: No such file or directory
???:1: open ../testdata/Mark.Twain-Tom.Sawyer.txt: No such file or
directory
FAIL
FAIL: compress/flate
I guess it's best to file two separate PRs for those issues.
Rainer
prev parent reply other threads:[~2012-02-16 19:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-22 19:43 [Bug go/48243] New: " ro at gcc dot gnu.org
2012-02-14 19:46 ` [Bug go/48243] " ian at airs dot com
2012-02-16 20:00 ` ro at CeBiTec dot Uni-Bielefeld.DE [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-48243-4-sAmuo8AcW5@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).