public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Andrew John Hughes" <gnu_andrew@member.fsf.org>
To: "Matthias Klose" <doko@ubuntu.com>
Cc: java@gcc.gnu.org, classpath@gnu.org
Subject: Re: GCJ Mauve testing
Date: Sat, 18 Oct 2008 23:13:00 -0000	[thread overview]
Message-ID: <17c6771e0810181612t5e0984a0p72b6860e5f8128d1@mail.gmail.com> (raw)
In-Reply-To: <48F9E6A2.6050304@ubuntu.com>

2008/10/18 Matthias Klose <doko@ubuntu.com>:
> Andrew John Hughes schrieb:
>> I've just run Mauve against both the 4.3 tree and our
>> Classpath 0.98 merge tree (effectively equivalent to Classpath
>> CVS + GCJ-specific changes).  Overall:
>>
>> 4.3:
>> 281 of 3177 tests failed.  123926 total calls to harness.check() failed.
>>
>> 4.4:
>> 239 of 3177 tests failed.  143832 total calls to harness.check() failed.
>>
>> There will be some new tests that compile with 4.4 but not 4.3 (e.g.
>> java.util.Scanner tests).
>
> Here is another run, done with trunk and branch 20081017.
>

Thanks for this.

> 4.3:
> 277 of 3175 tests failed.  139350 total calls to harness.check() failed.
>
> trunk:
> 232 of 3175 tests failed.  122871 total calls to harness.check() failed.
>
> merge branch (as 4.4 above):
> 229 of 3175 tests failed.  122914 total calls to harness.check() failed.
>
>> Additional FAILs are as follows:
>>
>> +FAIL: gnu.java.security.util.TestOfIntegerUtil
>> +FAIL: java.sql.Date.DateTest
>> +FAIL: java.lang.Character.Blocks15
>> +FAIL: java.lang.InheritableThreadLocal.simple
>> +FAIL: java.text.SimpleDateFormat.parse
>> +FAIL: java.util.Calendar.ampm
>> +FAIL: java.util.Scanner.LotsOfPMInts
>> +FAIL: java.util.Scanner.Inputs
>> +FAIL: javax.swing.text.DefaultStyledDocument.ElementBuffer.insert
>> +FAIL: javax.swing.table.JTableHeader.AccessibleJTableHeader.AccessibleJTableHeaderEntry.getForeground
>
> comparing 4.3 with the merge branch:
>
> 56 progressions and
>
> +FAIL: java.awt.TextField.PaintTest
> +FAIL: java.lang.ref.PhantomReference.phantom
> +FAIL: java.text.SimpleDateFormat.parse
> +FAIL: java.util.Calendar.ampm
> +FAIL: java.util.Scanner.FindWithinHorizon
> +FAIL: java.util.logging.Logger.getParent
> +FAIL: javax.swing.JButton.constructors
> +FAIL: javax.swing.text.DefaultStyledDocument.ElementBuffer.insert
>
> The following three go away if the cacerts file is in place.
>
> +FAIL: gnu.java.security.jce.TestOfHttps
> +FAIL: gnu.java.security.util.TestOfIntegerUtil
> +FAIL: java.net.URLConnection.getHeaderFields
>
> comparing the trunk with the merge branch (0.97.2 vs. 0.98pre):
>
> 9 progressions and
>
> +FAIL: gnu.java.security.util.TestOfIntegerUtil
> +FAIL: java.awt.Component.clickModifiers
> +FAIL: java.text.SimpleDateFormat.Localization
> +FAIL: java.util.Calendar.ampm
> +FAIL: java.util.Currency.US
> +FAIL: java.util.Scanner.FindWithinHorizon
> +FAIL: java.util.logging.Logger.getParent
>
> Full logs at http://people.ubuntu.com/~doko/java/mauve-results/
>
> libjava/testsuite/libjava.mauve doesn't work with current mauve, so all builds were installed, and
> mauve was run on the installed build.
>
>  Matthias
>
>

The Scanner tests can be written off, as they won't have compiled with
either 4.3 or trunk
(neither have java.util.Scanner).  The merge branch seems to be an
improvement, but there
are clearly some new localisation issues.

What is the plan for merging to trunk?
-- 
Andrew :-)

Support Free Java!
Contribute to GNU Classpath and the OpenJDK
http://www.gnu.org/software/classpath
http://openjdk.java.net

PGP Key: 94EFD9D8 (http://subkeys.pgp.net)
Fingerprint: F8EF F1EA 401E 2E60 15FA  7927 142C 2591 94EF D9D8

  reply	other threads:[~2008-10-18 23:13 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
2008-10-07  7:53       ` Andrew John Hughes
2008-10-18 13:38 ` Matthias Klose
2008-10-18 23:13   ` Andrew John Hughes [this message]
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=17c6771e0810181612t5e0984a0p72b6860e5f8128d1@mail.gmail.com \
    --to=gnu_andrew@member.fsf.org \
    --cc=classpath@gnu.org \
    --cc=doko@ubuntu.com \
    --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).