[
https://issues.apache.org/jira/browse/DERBY-5455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13125806#comment-13125806
]
Rick Hillegas commented on DERBY-5455:
--------------------------------------
That sounds like a good suggestion to me. The message seems like noise to me if
no-one is interested in tracking when a second attempt is needed to delete the
cruft.
It sounds as though the test itself will fail if we can't delete the cruft on
the second attempt. I think that means that the existing machinery will then
tell us which test tripped across the problem. That addresses my other
puzzlement with this diagnostic: I couldn't see which test was involved. Thanks.
> assertDirectoryDeleted diagnostic printed on console near end of running
> JUnit tests
> ------------------------------------------------------------------------------------
>
> Key: DERBY-5455
> URL: https://issues.apache.org/jira/browse/DERBY-5455
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.8.2.2
> Environment: mac os x 10.6.8, Java(TM) SE Runtime Environment (build
> 1.6.0_26-b03-384-10M3515)
> Reporter: Rick Hillegas
> Priority: Minor
>
> Near the end of the JUnit tests on the 10.8.2.2 RC, I saw the following
> diagnostic on the console. Don't know what test this refers to:
> .........................................
> .........................................
> .........................................
> .......................<assertDirectoryDeleted> attempt 1 left 3 files/dirs
> behind: 0=/Users/rh161140/derby/dummy/testRun/db_master/wombat/log
> 1=/Users/rh161140/derby/dummy/testRun/db_master/wombat
> 2=/Users/rh161140/derby/dummy/testRun/db_master
> ................
> Time: 4,221.94
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
