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-5664) Include driver tests in jdbcapi suite
Date Wed, 21 Mar 2012 21:12:38 GMT

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

Knut Anders Hatlen updated DERBY-5664:

    Attachment: d5664-1b-shutdown.diff

The 1a patch was only tested with a small part of jdbcapi, and when running the full suite
some problems showed up. The spawned test processes access the default test database, which
 is already booted in the main test process, and the spawned processes failed because attempts
to double-boot the database were detected.

Attaching an updated patch that adds a decorator that shuts down the database engine in the
main test process before spawning new test processes. With this change, suites.All ran successfully
in my environment.
> Include driver tests in jdbcapi suite
> -------------------------------------
>                 Key: DERBY-5664
>                 URL: https://issues.apache.org/jira/browse/DERBY-5664
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>    Affects Versions:
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>         Attachments: d5664-1a-jdbcapi-suite.diff, d5664-1b-shutdown.diff
> The tests AutoloadTest, JDBCDriversEmbeddedTest, JDBCDriversClientTest and JDBCDriversAllTest
are in the junit-all ant target but not in suites.All. We should make them part of the jdbcapi
suite so that they are picked up by suites.All too.

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


View raw message