db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2708) CanonTestCase keeps output from test in memory after it has finished
Date Sun, 27 May 2007 18:53:16 GMT

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

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

    Attachment: canon.diff

Attaching patch which adds tearDown() method to CanonTestCase and sets rawBytes to null.

> 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.


Mime
View raw message