Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 61159 invoked from network); 30 Jan 2006 02:50:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 30 Jan 2006 02:50:21 -0000 Received: (qmail 68471 invoked by uid 500); 30 Jan 2006 02:50:21 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 68439 invoked by uid 500); 30 Jan 2006 02:50:21 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 68430 invoked by uid 99); 30 Jan 2006 02:50:20 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 29 Jan 2006 18:50:20 -0800 X-ASF-Spam-Status: No, hits=1.9 required=10.0 tests=DNS_FROM_RFC_ABUSE,DNS_FROM_RFC_POST X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [32.97.182.144] (HELO e4.ny.us.ibm.com) (32.97.182.144) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 29 Jan 2006 18:50:20 -0800 Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236]) by e4.ny.us.ibm.com (8.12.11/8.12.11) with ESMTP id k0U2nwuM016358 for ; Sun, 29 Jan 2006 21:49:58 -0500 Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by d01relay04.pok.ibm.com (8.12.10/NCO/VERS6.8) with ESMTP id k0U2nwWO130856 for ; Sun, 29 Jan 2006 21:49:58 -0500 Received: from d01av03.pok.ibm.com (loopback [127.0.0.1]) by d01av03.pok.ibm.com (8.12.11/8.13.3) with ESMTP id k0U2nwfx017234 for ; Sun, 29 Jan 2006 21:49:58 -0500 Received: from [127.0.0.1] (sig-9-48-114-87.mts.ibm.com [9.48.114.87]) by d01av03.pok.ibm.com (8.12.11/8.12.11) with ESMTP id k0U2npGr017059 for ; Sun, 29 Jan 2006 21:49:57 -0500 Message-ID: <43DD7ECC.9040607@sbcglobal.net> Date: Sun, 29 Jan 2006 18:49:48 -0800 From: Kathey Marsden User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: derby-dev@db.apache.org Subject: Re: testing using remote host References: <43DCEA78.9000200@apache.org> <43DD6C95.9080203@apache.org> In-Reply-To: <43DD6C95.9080203@apache.org> X-Enigmail-Version: 0.85.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Daniel John Debrunner wrote: >The text in 4.14 scared me as it seems the setup for test when running >in remote mode is very different to running normally, thus increasing >the chance for some change to a test to break it in remote mode. Thus it >may be a never ending battle to keep the remote tests running. > > > It seems like all of the conditions are a function of either restrictions on remote access or useprocess itself, e.g. the need for database cleanup and the location of the extin files. It seems like ideally we would want those tests that run remotely to always run with useprocess=false when running with network server (or embedded for that manner). Then the needed test maintenance will be caught as a matter of normal development. [snip] >I don't see why database creation would fail, the policy file has >permissions to create databases under ${derby.system.home} and ${user.dir}. > > > I think the network server knows nothing about the test it is running or what directories to create. Consider this URL. jdbc:derby:net://my.remotehost.com:1527/wombat;user=howardR;password=takeItEasy Network server just has the derby.system.home it was started with and gets a database name "wombat", so all the tests that use that database name share a database. In local mode network server is restarted for each test in the appropriate directory. Kathey