db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ole Solberg (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3162) Create a framework for replication tests
Date Sat, 08 Mar 2008 09:55:46 GMT

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

Ole Solberg updated DERBY-3162:

    Attachment: derby-3162.4-v2.stat.txt

Patch derby-3162.4-v2 replaces derby-3162.4-v1:

This patch fixes some stupid classpath / pathSeparator problems which
also showed up on Windows.

I do however still have trouble running the tests on Windows:

I am seeing messages like 'Warning: UnknkownHostException: OLESO-FERRARI: OLESO-FERRARI.'
in connection with  InetAddress.getByName(hostName) in ReplicationRun.pingServer.

The patch therefore comments out the replication suite from suites.All.

'org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationSuite' must thus
be run 

I am sorry for the inconvenience :-(

> Create a framework for replication tests
> ----------------------------------------
>                 Key: DERBY-3162
>                 URL: https://issues.apache.org/jira/browse/DERBY-3162
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Test
>    Affects Versions:
>            Reporter: Ole Solberg
>            Assignee: Ole Solberg
>            Priority: Minor
>         Attachments: derby-3162.1-v1.diff.txt, derby-3162.2-v2.diff.txt, derby-3162.2-v2.stat.txt,
derby-3162.3-v1.diff.txt, derby-3162.3-v1.stat.txt, derby-3162.3-v2.diff.txt, derby-3162.3-v2.stat.txt,
derby-3162.3-v3.diff.txt, derby-3162.3-v3.stat.txt, derby-3162.3-v4c.diff.txt, derby-3162.3-v4c.stat.txt,
derby-3162.3-v4d.diff.txt, derby-3162.3-v4d.stat.txt, derby-3162.4-v1.diff.txt, derby-3162.4-v1.stat.txt,
derby-3162.4-v2.diff.txt, derby-3162.4-v2.stat.txt
> Handle
>  - starting and stopping Derby servers to have the master and slave replication roles,
>  - doing administrative commands like startreplication, startslave, stopreplication,
>  - performing consistency checks on the slave vs. the master,
>  - running load clients against master and slave in the various states of replication,
>  - provoking error situations on master and slave, and network,
>  - ... 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message