From: Andrew Haley <aph@redhat.com>
To: Andrew John Hughes <gnu_andrew@member.fsf.org>
Cc: java@gcc.gnu.org, classpath@gnu.org
Subject: Re: GCJ Mauve testing
Date: Tue, 07 Oct 2008 07:33:00 -0000 [thread overview]
Message-ID: <48EB10AC.70103@redhat.com> (raw)
In-Reply-To: <17c6771e0810061729nbd44918xd15216fa73446a5f@mail.gmail.com>
Andrew John Hughes wrote:
> 2008/10/6 Andrew Haley <aph@redhat.com>:
>> Andrew John Hughes wrote:
>>
>>> FAIL: java.lang.InheritableThreadLocal.simple
>>> Test timed out. Use -timeout [millis] option to change the timeout value.
>> This is strange, given that gcj has its own InheritableThreadLocal that
>> hasn't changed. I'll look.
>>
>> Andrew.
>>
>
> I did another Mauve run against the merge branch and gained some passes,
> but also some new failures:
>
> +PASS: gnu.java.security.util.TestOfIntegerUtil
> +PASS: java.awt.event.MouseEvent.modifiersEx
> +PASS: java.awt.event.MouseEvent.modifiers
> +PASS: java.util.logging.Logger.global
> +PASS: javax.swing.plaf.metal.MetalScrollBarUI.constructor
> +PASS: javax.swing.plaf.metal.MetalScrollBarUI.installDefaults
> +FAIL: java.util.logging.Logger.hierarchyChecks
> +FAIL: java.util.logging.Logger.securityChecks
> +FAIL: java.util.logging.SocketHandler.getFormatter
> +FAIL: java.util.Scanner.DoubleFloat
> +FAIL: java.util.Scanner.FishString
> +FAIL: java.util.Scanner.Radix
> +FAIL: javax.sound.sampled.AudioProperties
> +FAIL: javax.swing.JTable.TableRobot
>
> Odd to say the least.
Curious. It's not immediately obvious how the change could have affected
those, but I'll have a look.
Andrew.
next prev parent reply other threads:[~2008-10-07 7:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-26 23:06 Andrew John Hughes
2008-09-26 23:16 ` Andrew John Hughes
2008-10-06 9:12 ` Andrew Haley
2008-10-07 0:30 ` Andrew John Hughes
2008-10-07 7:33 ` Andrew Haley [this message]
2008-10-07 7:53 ` Andrew John Hughes
2008-10-18 13:38 ` Matthias Klose
2008-10-18 23:13 ` Andrew John Hughes
2008-10-19 9:17 ` Andrew Haley
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=48EB10AC.70103@redhat.com \
--to=aph@redhat.com \
--cc=classpath@gnu.org \
--cc=gnu_andrew@member.fsf.org \
--cc=java@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).