From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8465 invoked by alias); 24 Jul 2007 11:21:08 -0000 Received: (qmail 8391 invoked by uid 48); 24 Jul 2007 11:20:58 -0000 Date: Tue, 24 Jul 2007 11:21:00 -0000 From: "kris dot van dot hees at oracle dot com" To: frysk-bugzilla@sourceware.org Message-ID: <20070724112058.4837.kris.van.hees@oracle.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug general/4837] New: Incorrect junit output from frysk.proc.live.TestByteBuffer X-Bugzilla-Reason: AssignedTo Mailing-List: contact frysk-bugzilla-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: frysk-bugzilla-owner@sourceware.org X-SW-Source: 2007-q3/txt/msg00159.txt.bz2 List-Id: 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.