Return-Path: 
 <derby-dev-return-4794-apmail-db-derby-dev-archive=db.apache.org@db.apache.org>
Delivered-To: apmail-db-derby-dev-archive@www.apache.org
Received: (qmail 1636 invoked from network); 27 May 2005 00:44:51 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 27 May 2005 00:44:51 -0000
Received: (qmail 43599 invoked by uid 500); 27 May 2005 00:44:50 -0000
Delivered-To: apmail-db-derby-dev-archive@db.apache.org
Received: (qmail 43559 invoked by uid 500); 27 May 2005 00:44:50 -0000
Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:derby-dev-help@db.apache.org>
list-unsubscribe: <mailto:derby-dev-unsubscribe@db.apache.org>
List-Post: <mailto:derby-dev@db.apache.org>
List-Id: <derby-dev.db.apache.org>
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Delivered-To: mailing list derby-dev@db.apache.org
Received: (qmail 43546 invoked by uid 99); 27 May 2005 00:44:50 -0000
X-ASF-Spam-Status: No, hits=2.2 required=10.0
	tests=DNS_FROM_RFC_ABUSE,DNS_FROM_RFC_POST,SPF_HELO_FAIL
X-Spam-Check-By: apache.org
Received-SPF: neutral (hermes.apache.org: local policy)
Received: from e35.co.us.ibm.com (HELO e35.co.us.ibm.com) (32.97.110.133)
  by apache.org (qpsmtpd/0.28) with ESMTP; Thu, 26 May 2005 17:44:46 -0700
Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com
 [9.17.195.11])
	by e35.co.us.ibm.com (8.12.10/8.12.9) with ESMTP id j4R0iYMK629540
	for <derby-dev@db.apache.org>; Thu, 26 May 2005 20:44:34 -0400
Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com
 [9.17.195.170])
	by westrelay02.boulder.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id
 j4R0iYhT212816
	for <derby-dev@db.apache.org>; Thu, 26 May 2005 18:44:34 -0600
Received: from d03av04.boulder.ibm.com (loopback [127.0.0.1])
	by d03av04.boulder.ibm.com (8.12.11/8.13.3) with ESMTP id j4R0iYEI001394
	for <derby-dev@db.apache.org>; Thu, 26 May 2005 18:44:34 -0600
Received: from [127.0.0.1] (Abrown.svl.ibm.com [9.30.40.217])
	by d03av04.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id j4R0iX8u001381
	for <derby-dev@db.apache.org>; Thu, 26 May 2005 18:44:33 -0600
Message-ID: <42966D9C.5050403@sbcglobal.net>
Date: Thu, 26 May 2005 17:45:16 -0700
From: Army <qozinx@sbcglobal.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.7.1) Gecko/20040707
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Derby Development <derby-dev@db.apache.org>
Subject: Re: [jira] Updated: (DERBY-230) "Schema already exists" when creating
 a table
References: <1292804070.1116587761316.JavaMail.jira@ajax.apache.org>
 <x1ofmzqj5ra1.fsf@atum11.Norway.Sun.COM> <42961193.2070601@sbcglobal.net>
 <42961DC7.4000409@sbcglobal.net> <x1ofzmuhy52p.fsf@gong1.norway.sun.com>
In-Reply-To: <x1ofzmuhy52p.fsf@gong1.norway.sun.com>
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Virus-Checked: Checked
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

�ystein Gr�vlen wrote:

> I must admit that I did not understand what was needed to get it to
> run as part of the network server test.  I am still a bit confused,

I agree that this can be confusing.  There is some documentation on the harness 
here:

https://svn.apache.org/viewcvs.cgi/*checkout*/incubator/derby/code/trunk/java/testing/README.htm

but maybe you've already read that and are still uncertain?

In a word, there are suites and there are sub-suites.  For a given suite 
<suiteA>, all of the tests in <suiteA>.runall are run, PLUS all of the 
sub-suites listed in the "suites" property of the <suiteA>.properties file. 
Sub-suites are run using their own properties PLUS any properties inherited from 
their parent suite.  If the parent suite and subsuite both define a property, 
the parent suite's property takes precedence.

That said, the suite that gets run every night is the "derbyall" suite.  So in 
order for a test to run every night, it must be part of a subsuite (either 
directly or through several depths of recursion) that is specified in the 
"suites" property of the derbyall.properties file.

One of the subsuites that derbyall runs is "derbynetmats", which will run all of 
the tests listed in derbynetmats.runall PLUS four other sub-suites listed in 
derbynetmats.properties.  Since the "framework" property in 
derbynetmats.properties is "DerbyNet", that means that all tests/sub-suites run 
from derbynetmats will run against the server using the JCC driver.

*SO*, in order to make a test run against the server every night, you have to 
ensure that one of the following is true:

1) the test is included (either directly or by recursion) in one of the 
subsuites listed in derbynetmats.properties,
OR
2) the test is listed in derbynetmats.runall.

In your case, since the ConcurrentImplicitCreateSchema.java test isn't part of 
any of the sub-suites listed in derbynetmats.properties (it's in the "derbylang" 
suite), you have to add it to the derbynetmats.runall file.

I don't think that's as clear as I'd like it to be, but hopefully it helps.  And 
if it doesn't...well, the important thing is that you add your new test to the 
"derbynetmats.runall", and trust that that'll work ;)

> I will do this and resubmit the patch.  Should it also be added to the
> derbynetclientmats.runall? 

The "derbynetclientmats" suite has "derbynetmats" as a sub-suite.  That means 
that all files in derbynetmats.runall will be run as part of derbynetclientmats, 
as well.  Thus, if you add your new test to derbynetmats.runall, you will NOT 
have to add it to derbynetclientmats.runall; it will be included by recursion.

Hope that helps,
Army