db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5297) noConnectionAfterHardUpgrade in upgrade test fails intermittently (file deletion)
Date Thu, 18 Aug 2011 07:50:27 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086866#comment-13086866
] 

Kristian Waagan commented on DERBY-5297:
----------------------------------------

Another occurrence (2011-08-16): http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/testlog/w2003/1158340-suitesAll_diff.txt


> noConnectionAfterHardUpgrade in upgrade test fails intermittently (file deletion)
> ---------------------------------------------------------------------------------
>
>                 Key: DERBY-5297
>                 URL: https://issues.apache.org/jira/browse/DERBY-5297
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.9.0.0
>         Environment: Windows
>            Reporter: Kristian Waagan
>            Priority: Minor
>         Attachments: derby-5297-1a-move_db_experiment.diff
>
>
> The test fixture noConnectionAfterHardUpgrade in the upgrade test fails intermittently
on Windows platforms. The symptom is that some of the database files cannot be deleted.
> Example failure (excerpt, shortened paths, formatted):
> 1) Upgrade Tests from 10.8.1.2junit.framework.AssertionFailedError: Failed to delete
3 files (root=singleUse\oneuseb2:
>     singleUse\oneuseb2\seg0\c790.dat   (isDir=false, canRead=true, canWrite=true, size=8192),
>     singleUse\oneuseb2\seg0                (isDir=true, canRead=true, canWrite=true,
size=65536),
>     singleUse\oneuseb2                        (isDir=true, canRead=true, canWrite=true,
size=0)
> Log:
> (2011-06-25) http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/testlog/vista/1139564-suitesAll_diff.txt
> I think I've seen this failure before, but couldn't find it in the test logs.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message