db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-5504) SecureServerTest, Driver40UnbootedTest and replication tests not prepared for space in java.home
Date Thu, 17 Nov 2011 09:26:51 GMT

     [ https://issues.apache.org/jira/browse/DERBY-5504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Knut Anders Hatlen updated DERBY-5504:
--------------------------------------

    Issue & fix info:   (was: Patch Available)

Thanks for looking at the patch, Dag.

Committed revision 1203113.

Yes, I intend to do something similar for the replication tests, but it looks as if more changes
are needed for them, especially for the code that supports running tests against remote hosts.
I don't think anyone has run the replication tests against remote hosts for a very long time,
and given the instabilities we see when running the tests locally, I suspect there are even
more problems. Maybe it's easier just to remove that code. There hasn't been much interest
in improving the replication tests lately, and simplifying the tests by removing the code
that supports remote testing might in fact make it easier to maintain the parts of the replication
tests that we actually use in the daily testing.
                
> SecureServerTest, Driver40UnbootedTest and replication tests not prepared for space in
java.home
> ------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5504
>                 URL: https://issues.apache.org/jira/browse/DERBY-5504
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.9.0.0
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>         Attachments: d5504-1a.diff
>
>
> SecureServerTest, Driver40UnbootedTest and the replication tests fork JVMs by calling
Runtime.exec() methods that take the command as a String parameter, not a String[]. This causes
problems like the ones seen in DERBY-5490 when there's a space in ${java.home}.
> The tests should be rewritten to use the helper method BaseTestCase.execJavaCmd(), which
handles this case correctly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message