Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <16065784.1180291996851.JavaMail.jira@brutus>
Date: Sun, 27 May 2007 11:53:16 -0700 (PDT)
From: "Knut Anders Hatlen (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-2708) CanonTestCase keeps output from test
 in memory after it has finished
In-Reply-To: <9238643.1180291876513.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DERBY-2708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Knut Anders Hatlen updated DERBY-2708:
--------------------------------------

    Component/s:     (was: Tools)
                 Test

> CanonTestCase keeps output from test in memory after it has finished
> --------------------------------------------------------------------
>
>                 Key: DERBY-2708
>                 URL: https://issues.apache.org/jira/browse/DERBY-2708
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.3.0.0
>            Reporter: Knut Anders Hatlen
>         Assigned To: Knut Anders Hatlen
>            Priority: Minor
>         Attachments: canon.diff
>
>
> CanonTestCase has a ByteArrayOutputStream which contains the output from the test. The stream is not nulled out when the test has finished, so all the output stays in memory. (The stream is actually closed in compareCanon(), but ByteArrayOutputStream's javadoc says that closing it has no effect.)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.