[
https://issues.apache.org/jira/browse/DERBY-6610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14169739#comment-14169739
]
Myrna van Lunteren commented on DERBY-6610:
-------------------------------------------
Re Derby3980DeadlockTest: the test failed because of a missing "read"
permission as well as the missing usederbyinternals permission. Also there was
a typo in one permssion granted.
Note further that this test is not part of suites.All, according to DERBY-3980
it was considered not stable so has not been added to any suite. Furthermore,
it was replaced by DeadlockDetectionTest, so one way to deal with this is to
just remove the test and its policy file.
However, for now, I'll just patch up the Derby3980DeadlockTest.policy.
> suites.All cannot be run with classes without failures
> ------------------------------------------------------
>
> Key: DERBY-6610
> URL: https://issues.apache.org/jira/browse/DERBY-6610
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.11.1.1
> Reporter: Myrna van Lunteren
> Assignee: Myrna van Lunteren
> Priority: Minor
> Attachments: DERBY-6610_1.diff, DERBY-6610_pols1.diff,
> tmp-permission.diff
>
>
> suites.All no longer runs cleanly for me when I run with just classes.
> It still runs fine with jars.
> We accepted this behavior at some point, but it is frustrating when you want
> to 'quickly' run tests while still working on some details.
> One of the tests that failed for me was lang.DatabaseClassLoadingTest
> (complaining about one of the databases not found), another was
> lang.LuceneSupportPermsTest.
> If a test cannot run cleanly with classes, it should get skipped (preferably
> both in the test itself and from the _Suite in which it is included).
> I also think some of the network server tests complain if derbynet.jar is not
> found - I cannot off-hand remember if this causes the test to fail.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
