public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Tom Tromey <tromey@redhat.com>
Cc: Frysk List <frysk@sourceware.org>
Subject: Re: minor frysk cleanup
Date: Sat, 01 Mar 2008 19:22:00 -0000	[thread overview]
Message-ID: <1204399331.3279.34.camel@localhost.localdomain> (raw)
In-Reply-To: <m3d4qegxc0.fsf@fleche.redhat.com>

Hi Tom,

On Sat, 2008-03-01 at 10:37 -0700, Tom Tromey wrote:
> Mark> This looks good. Thanks.
> Mark> If you have git push access please push it.
> Mark> Otherwise I can do that for you.
> 
> I don't think I do.

OK, I pushed it for you.

> Mark> It does help if you run make check in at least frysk-core (or make check
> Mark> -k toplevel) and mention whether you see any failures (normally we
> Mark> should have zero fails, at least in frysk-core).
> 
> I will run it now.

As discussed on irc there are currently some failures :{
Those are not supposed to be there of course, normally we are pretty
good at staying at zero fail. I checked that there were no regressions
with your patch applied (same results before/after).

Thanks,

Mark

Just for the record this is the failure list from frysk-core
(fedora 8, x86):

There were 2 unsupported:
  disassembler
  requires both 32-bit and 64-bit
There were 3 failures:
1)
testComplexStruct(frysk.value.TestClass)junit.framework.ComparisonFailure: Variable is a struct expected:<struct> but was:<class>
   at frysk.value.TestClass.testComplexStruct(TestRunner)
   at frysk.junit.Runner.runCases(TestRunner)
   at frysk.junit.Runner.runTestCases(TestRunner)
   at TestRunner.main(TestRunner)
2)
testInheritedStruct(frysk.value.TestClass)junit.framework.ComparisonFailure: Variable is a struct expected:<struct> but was:<class>
   at frysk.value.TestClass.testInheritedStruct(TestRunner)
   at frysk.junit.Runner.runCases(TestRunner)
   at frysk.junit.Runner.runTestCases(TestRunner)
   at TestRunner.main(TestRunner)
3)
testPublicPrivateType(frysk.value.TestComposite)junit.framework.ComparisonFailure: toPrint expected:<...public:
 ...> but was:<......>
   at frysk.value.TestComposite.testPublicPrivateType(TestRunner)
   at frysk.junit.Runner.runCases(TestRunner)
   at frysk.junit.Runner.runTestCases(TestRunner)
   at TestRunner.main(TestRunner)

FAILURES!!!
Tests run: 981,  Failures: 3,  Errors: 0

Failed after run #0
Exception in thread "main" FAIL: TestRunner
java.lang.NullPointerException
   at FunitSimpleInterfaceTest.main(FunitSimpleInterfaceTest.java:46)
Exception in thread "main" java.lang.NullPointerException
   at FunitSimpleInterfaceTest.main(FunitSimpleInterfaceTest.java:46)
FAIL: frysk/pkglibdir/FunitSimpleInterfaceTest
no suitable method `main' in class
FAIL: frysk/rt/TestDisplayValue


  reply	other threads:[~2008-03-01 19:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-29 21:10 Tom Tromey
2008-03-01 18:16 ` Mark Wielaard
2008-03-01 18:27   ` Tom Tromey
2008-03-01 19:22     ` Mark Wielaard [this message]
2008-03-01 19:27       ` Tom Tromey

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=1204399331.3279.34.camel@localhost.localdomain \
    --to=mark@klomp.org \
    --cc=frysk@sourceware.org \
    --cc=tromey@redhat.com \
    /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).