db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6610) suites.All cannot be run with classes without failures
Date Wed, 15 Oct 2014 23:41:34 GMT

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

ASF subversion and git services commented on DERBY-6610:

Commit 1632198 from [~myrna] in branch 'code/trunk'
[ https://svn.apache.org/r1632198 ]

DERBY-6610; suites.All cannot be run with classes without failures
   grant DeclaredMember permission to the codeclasses area in policy file for lucene tests.

> 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:
>            Reporter: Myrna van Lunteren
>            Assignee: Myrna van Lunteren
>            Priority: Minor
>         Attachments: DERBY-6610_1.diff, DERBY-6610_pols1.diff, DERBY-6610_pols3.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

View raw message