public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "dominiq at lps dot ens dot fr" <gcc-bugzilla@gcc.gnu.org> To: java-prs@gcc.gnu.org Subject: [Bug java/35035] [4.3 Regression] Has any one managed to run the libjava test suite on powerpc-apple-darwin9? Date: Sun, 03 Feb 2008 21:57:00 -0000 [thread overview] Message-ID: <20080203215732.8464.qmail@sourceware.org> (raw) In-Reply-To: <bug-35035-12313@http.gcc.gnu.org/bugzilla/> ------- Comment #23 from dominiq at lps dot ens dot fr 2008-02-03 21:57 ------- My machine is a G5 1.8Ghz mono processor, 1.5Gb of memory. The symptom is very close to the one described in comment #19, excepted that the failure occurs for different test cases and so far I have been unable to interrupt the test with a ^C, I had always to reboot the machine. Also the only info I have is the last record in libjava.log, the problem may be occur later without leaving any trace(?). On intel-darwin9 I have the following failures: === libjava tests === Running target unix FAIL: /opt/gcc/gcc-4.3-work/libjava/testsuite/libjava.jar/TestClosureGC.jar execution - gij test === libjava Summary for unix === # of expected passes 2548 # of unexpected failures 1 # of untested testcases 1 Running target unix/-m64 FAIL: PR16923 run FAIL: events output === libjava Summary for unix/-m64 === # of expected passes 2548 # of unexpected failures 2 # of untested testcases 1 === libjava Summary === # of expected passes 5096 # of unexpected failures 3 # of untested testcases 2 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35035
next prev parent reply other threads:[~2008-02-03 21:57 UTC|newest] Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-01-30 22:10 [Bug java/35035] New: " dominiq at lps dot ens dot fr 2008-01-30 22:13 ` [Bug java/35035] " dominiq at lps dot ens dot fr 2008-01-30 22:18 ` andreast at gcc dot gnu dot org 2008-01-31 9:49 ` [Bug java/35035] [4.3 Regression] " rguenth at gcc dot gnu dot org 2008-01-31 10:01 ` dominiq at lps dot ens dot fr 2008-01-31 10:11 ` rguenth at gcc dot gnu dot org 2008-01-31 10:12 ` rguenth at gcc dot gnu dot org 2008-01-31 10:35 ` dominiq at lps dot ens dot fr 2008-01-31 11:12 ` andreast at gcc dot gnu dot org 2008-01-31 12:28 ` dominiq at lps dot ens dot fr 2008-01-31 12:51 ` andreast at gcc dot gnu dot org 2008-01-31 13:30 ` andreast at gcc dot gnu dot org 2008-01-31 14:14 ` rguenth at gcc dot gnu dot org 2008-01-31 14:19 ` rguenth at gcc dot gnu dot org 2008-01-31 18:39 ` andreast at gcc dot gnu dot org 2008-01-31 23:10 ` dominiq at lps dot ens dot fr 2008-02-03 12:46 ` rguenth at gcc dot gnu dot org 2008-02-03 20:47 ` dominiq at lps dot ens dot fr 2008-02-03 20:56 ` dominiq at lps dot ens dot fr 2008-02-03 21:22 ` andreast at gcc dot gnu dot org 2008-02-03 21:40 ` rguenth at gcc dot gnu dot org 2008-02-03 21:40 ` rguenth at gcc dot gnu dot org 2008-02-03 21:42 ` howarth at nitro dot med dot uc dot edu 2008-02-03 21:57 ` dominiq at lps dot ens dot fr [this message] 2008-02-03 22:08 ` andreast at gcc dot gnu dot org 2008-02-03 22:15 ` dominiq at lps dot ens dot fr 2008-02-03 22:19 ` howarth at nitro dot med dot uc dot edu 2008-02-04 13:32 ` dominiq at lps dot ens dot fr 2008-02-04 13:48 ` andreast at gcc dot gnu dot org 2008-02-04 14:01 ` dominiq at lps dot ens dot fr 2008-02-04 14:54 ` howarth at nitro dot med dot uc dot edu 2008-02-04 18:36 ` howarth at nitro dot med dot uc dot edu 2008-02-04 20:39 ` rguenther at suse dot de 2008-02-04 21:13 ` rguenth at gcc dot gnu dot org 2008-02-04 21:13 ` rguenth at gcc dot gnu dot org 2008-02-05 19:27 ` dominiq at lps dot ens dot fr 2008-02-05 19:58 ` howarth at nitro dot med dot uc dot edu 2008-02-05 20:01 ` pinskia at gmail dot com 2008-02-05 20:10 ` rguenther at suse dot de 2008-02-05 20:13 ` howarth at nitro dot med dot uc dot edu 2008-02-05 20:26 ` dominiq at lps dot ens dot fr 2008-02-05 20:30 ` rguenther at suse dot de 2008-03-12 14:26 ` rguenth at gcc dot gnu dot org 2008-03-12 14:30 ` rguenth at gcc dot gnu dot org
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=20080203215732.8464.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=java-prs@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: linkBe 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).