public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: pearly.zhao@oracle.com
Cc: Andrew Cagney <cagney@redhat.com>, frysk@sourceware.org
Subject: Re: [SCM]  master: Add a test 	testMemoryBufferCapacity()	to	TestByteBuffer.java
Date: Thu, 29 Nov 2007 10:44:00 -0000	[thread overview]
Message-ID: <1196332968.27594.11.camel@dijkstra.wildebeest.org> (raw)
In-Reply-To: <1196332579.27594.8.camel@dijkstra.wildebeest.org>

On Thu, 2007-11-29 at 11:36 +0100, Mark Wielaard wrote:
> Congrats, it does PASS on x86 and x86_64. And more congrats, since you
> seem to have caught a bug on 32bit-on-64bit systems! If you run the test
> on a x86_64 system with ./TestRunner -arch 32
> frysk.proc.live.TestByteBuffer.testMemoryBufferCapacity you get:
> [... nothing ...]

Doh. Of course it helps if I actually paste the output:

1)
testMemoryBufferCapacity(frysk.proc.live.TestByteBuffer)junit.framework.AssertionFailedError: Memory Buffer Capacity:  expected:<4294967295> but was:<-1>
   at
frysk.proc.live.TestByteBuffer.testMemoryBufferCapacity(TestRunner)
   at frysk.junit.Runner.runCases(TestRunner)
   at frysk.junit.Runner.runArch32Cases(TestRunner)
   at frysk.junit.Runner.runTestCases(TestRunner)
   at TestRunner.main(TestRunner)

> http://sourceware.org/bugzilla/show_bug.cgi?id=5432
> If someone knows how to fix this properly you now have a testcase!


      reply	other threads:[~2007-11-29 10:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20071122090733.7335.qmail@sourceware.org>
2007-11-22 17:10 ` Andrew Cagney
2007-11-23  4:10   ` Zhao Shujing
2007-11-24  0:07     ` Andrew Cagney
2007-11-26  2:53       ` Zhao Shujing
2007-11-27 14:45         ` Andrew Cagney
2007-11-28  8:21           ` Zhao Shujing
2007-11-29 10:37             ` Mark Wielaard
2007-11-29 10:44               ` Mark Wielaard [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=1196332968.27594.11.camel@dijkstra.wildebeest.org \
    --to=mark@klomp.org \
    --cc=cagney@redhat.com \
    --cc=frysk@sourceware.org \
    --cc=pearly.zhao@oracle.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).