From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28472 invoked by alias); 14 Apr 2002 13:16:04 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 28432 invoked by uid 71); 14 Apr 2002 13:16:01 -0000 Resent-Date: 14 Apr 2002 13:16:01 -0000 Resent-Message-ID: <20020414131601.28431.qmail@sources.redhat.com> Resent-From: gcc-gnats@gcc.gnu.org (GNATS Filer) Resent-To: nobody@gcc.gnu.org Resent-Cc: gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org, java-prs@gcc.gnu.org Resent-Reply-To: gcc-gnats@gcc.gnu.org, mark@klomp.org Received:(qmail 26911 invoked by uid 61); 14 Apr 2002 13:12:13 -0000 Message-Id:<20020414131213.26910.qmail@sources.redhat.com> Date: Sun, 14 Apr 2002 06:16:00 -0000 From: mark@klomp.org Reply-To: mark@klomp.org To: gcc-gnats@gcc.gnu.org X-Send-Pr-Version:gnatsweb-2.9.3 (1.1.1.1.2.31) Subject: libgcj/6293: PipedInputStream.close() does not notify writer (Mauve test) X-SW-Source: 2002-04/txt/msg00737.txt.bz2 List-Id: >Number: 6293 >Category: libgcj >Synopsis: PipedInputStream.close() does not notify writer (Mauve test) >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Sun Apr 14 06:16:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: mark@klomp.org >Release: gcj 3.1 >Organization: >Environment: >Description: According to the Mauve testlet gnu.testlet.java.io.PipedStream.close the PipedInputStream.close() method should notify the associated PipedOutputStream of the close. We currently faily this test. But the testlet looks like it is actually testing wether a PipedInputStream.read() will return -1 when PipedInputStream.close() is called in another Thread. Anyway we fail this test. >How-To-Repeat: echo gnu.testlet.java.io.PipedStream.close | ./SimpleTestHarness >Fix: >Release-Note: >Audit-Trail: >Unformatted: