You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Knut Anders Hatlen (JIRA)" <ji...@apache.org> on 2007/05/27 20:55:16 UTC

[jira] Resolved: (DERBY-2708) CanonTestCase keeps output from test in memory after it has finished

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

Knut Anders Hatlen resolved DERBY-2708.
---------------------------------------

       Resolution: Fixed
    Fix Version/s: 10.3.0.0

Committed revision 542019.

> 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
>             Fix For: 10.3.0.0
>
>         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.