db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-871) remote host support in test harness needs more work
Date Mon, 06 Feb 2006 19:01:11 GMT
     [ http://issues.apache.org/jira/browse/DERBY-871?page=all ]

Myrna van Lunteren updated DERBY-871:

    Attachment: DERBY-871-020606.stat

The new patch, DERBY-871_020606.*, has 2 basic purposes:
- remove the need for useprocess false with remote server configuration
- fix up some tests so they can run in remote server configuration
contains the following changes:
M      java\drda\org\apache\derby\impl\drda\TestProto.java
              fixed up dependency on useprocess false directory structure with hostName !=
M      java\testing\README.htm
            -  removed references to useprocess false in -DhostName section
            -  added more few comments to useprocess to explain impact better
            -  in passing fixed up path referene to multi tests as reported by someone on
the list
            -  removed the 'last updated ' line - anyone updating the doc forgets
                  to do modify this  (incl. me), so really should rely on version control
info for this.          
M      java\testing\org\apache\derbyTesting\functionTests\tests\lang\syscat_app.properties
                 make syscat create its own database. This way, the test may be run in remote
                 configuration without relying on all other tests to be clean
M      java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\resultset.java
                 test was not properly cleaning up after itself
M      java\testing\org\apache\derbyTesting\functionTests\tests\derbynet\testSecMec.java
                 because of placing of InetAddres.getByName call, an additional socketPermission,
                 was needed for derbyTesting.jar in remote server configuration, for which
I couldn't see
                 the point, as it is not a call specific to derby. 
M      java\testing\org\apache\derbyTesting\functionTests\tests\derbynet\prepStmt.java
                 test was not properly cleaning up after itself
M      java\testing\org\apache\derbyTesting\functionTests\harness\RunTest.java
                 remove useprocess=false when hostName != localhost
M      java\testing\org\apache\derbyTesting\functionTests\suites\DerbyNetRemote.exclude
M      java\testing\org\apache\derbyTesting\functionTests\suites\DerbyNetClientRemote.exclude
                adjust comments to no longer refer to useprocess, enable lang/syscat.sql

I ran derbyall, as well as derbynetmats and derbynetclientmats against a remote server, with
insane jars.
There were no failures.

> remote host support in test harness needs more work
> ---------------------------------------------------
>          Key: DERBY-871
>          URL: http://issues.apache.org/jira/browse/DERBY-871
>      Project: Derby
>         Type: Bug
>   Components: Test
>     Versions:
>     Reporter: Myrna van Lunteren
>     Assignee: Myrna van Lunteren
>     Priority: Minor
>  Attachments: DERBY-871-020606.diff, DERBY-871-020606.stat, DERBY-874-012906.diff, DERBY-874-012906.stat
> With the changes to have security manager run for tests with useprocess=false, the remote
host support in the test harness no l onger works.
> permissions need to be passed in derby_test.policy for the client.
> There is no technical reason for the remote host support to be useprocess=false.
> The readme needs to be updated.
> Also, there are some other changes that have caused for database objects to be left behind,
which is a problem because with remote host, databases are re-used.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message