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-4804) Make database used in store.OSReadOnlyTest fully read-only
Date Thu, 23 Sep 2010 18:43:32 GMT

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

Kristian Waagan commented on DERBY-4804:

Thanks for running the test on more platforms, Myrna.

If the shell and the OS, possibly Java as well, aren't able to cooperate properly, there isn't
much we can do except to accept both error messages.
Unless you discover something crucial, I would suggest we allow both 25502 and 40XD1.

Another experiment you can do, is to enable the line setting directories to read-only (currently
commented out). This is not a solution to the problem, but it may get you past the current
point of failure. The test should then fail when trying to delete the files instead.

> Make database used in store.OSReadOnlyTest fully read-only
> ----------------------------------------------------------
>                 Key: DERBY-4804
>                 URL: https://issues.apache.org/jira/browse/DERBY-4804
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>    Affects Versions:
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>            Priority: Minor
>             Fix For:
>         Attachments: derby-4804-1a-test_change.diff, derby-4804-2a-common_file_ops.diff
> store.OSReadOnlyTest is supposed to emulate running Derby on a read-only media, but it
turns out the database directory isn't made read-only - only the files inside the directories
> See http://db.markmail.org/thread/f3qlfx7teg7yk5hr for more details.

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

View raw message