public inbox for frysk-bugzilla@sourceware.org help / color / mirror / Atom feed
From: "kris dot van dot hees at oracle dot com" <sourceware-bugzilla@sourceware.org> To: frysk-bugzilla@sourceware.org Subject: [Bug general/4837] New: Incorrect junit output from frysk.proc.live.TestByteBuffer Date: Tue, 24 Jul 2007 11:21:00 -0000 [thread overview] Message-ID: <20070724112058.4837.kris.van.hees@oracle.com> (raw) During automated build-and-test runs the following output was captured. Note the duplication of reporting on most tests, often with two different results! It also seems to continue into the next class of tests, indicating it is most likely another case where test case problems are messing up junit's functionality. Running testSliceAddressSpace(frysk.proc.live.TestByteBuffer) ...FAIL junit.framework.AssertionFailedError: unexpected signal Sig_IO Running testSliceMemorySpace(frysk.proc.live.TestByteBuffer) ...PASS Running testSliceRegisterSet(frysk.proc.live.TestByteBuffer) ...ERROR close: Bad file descriptor (fd 0) Running testModifyRegisterSet(frysk.proc.live.TestByteBuffer) ...PASS Running testModifyRegisterSet(frysk.proc.live.TestByteBuffer) ...ERROR close: Bad file descriptor (fd 0) Running testModifyAddressSpace(frysk.proc.live.TestByteBuffer) ...PASS Running testModifyAddressSpace(frysk.proc.live.TestByteBuffer) ...ERROR close: Bad file descriptor (fd 0) Running testModifyMemorySpace(frysk.proc.live.TestByteBuffer) ...PASS Running testModifyMemorySpace(frysk.proc.live.TestByteBuffer) ...ERROR close: Bad file descriptor (fd 0) Running testAsyncRegisterSet(frysk.proc.live.TestByteBuffer) ...PASS Running testAsyncRegisterSet(frysk.proc.live.TestByteBuffer) ...ERROR close: Bad file descriptor (fd 0) Running testAsyncAddressSpace(frysk.proc.live.TestByteBuffer) ...PASS Running testAsyncAddressSpace(frysk.proc.live.TestByteBuffer) ...PASS Running testAsyncMemorySpace(frysk.proc.live.TestByteBuffer) ...ERROR close: Bad file descriptor (fd 0) Running testPeeks(frysk.proc.live.TestMemorySpaceByteBuffer) ...PASS Running testPeeks(frysk.proc.live.TestMemorySpaceByteBuffer) ...ERROR close: Bad file descriptor (fd 0) Running testAsyncPeeks(frysk.proc.live.TestMemorySpaceByteBuffer) ...PASS Running testAsyncPeeks(frysk.proc.live.TestMemorySpaceByteBuffer) ...ERROR close: Bad file descriptor (fd 0) Running testAbandonThenRemoveAckDaemon(frysk.proc.TestAbandon) ...PASS Running testAbandonThenRemoveAckDaemon(frysk.proc.TestAbandon) ...PASS Running testAbandonThenRemoveDetached(frysk.proc.TestAbandon) ...PASS Running testAbandonThenRemoveAttached(frysk.proc.TestAbandon) ...ERROR open: Success (file /proc/465/stat) Running testAbandonThenRemoveAckDaemonUpdateExecuted(frysk.proc.TestAbandon) ... -- Summary: Incorrect junit output from frysk.proc.live.TestByteBuffer Product: frysk Version: unspecified Status: NEW Severity: normal Priority: P2 Component: general AssignedTo: frysk-bugzilla at sourceware dot org ReportedBy: kris dot van dot hees at oracle dot com http://sourceware.org/bugzilla/show_bug.cgi?id=4837 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
reply other threads:[~2007-07-24 11:21 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20070724112058.4837.kris.van.hees@oracle.com \ --to=sourceware-bugzilla@sourceware.org \ --cc=frysk-bugzilla@sourceware.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).