Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 52661 invoked from network); 23 Sep 2010 02:30:42 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 23 Sep 2010 02:30:42 -0000 Received: (qmail 18608 invoked by uid 500); 23 Sep 2010 02:30:42 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 18454 invoked by uid 500); 23 Sep 2010 02:30:42 -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 18443 invoked by uid 99); 23 Sep 2010 02:30:41 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Sep 2010 02:30:41 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of msatoor@gmail.com designates 209.85.216.44 as permitted sender) Received: from [209.85.216.44] (HELO mail-qw0-f44.google.com) (209.85.216.44) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Sep 2010 02:30:35 +0000 Received: by qwc9 with SMTP id 9so965520qwc.31 for ; Wed, 22 Sep 2010 19:30:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=U05ALnUS1bt+KxVYIHynt8PEFueGkNWhZFjLg7YwJeE=; b=B6cQAqSQGRe+Kre17gYbWOXrmRwscI40q6oQowNIkAYJzFhDI8N23MRaO62AiIgAnf t7ah+2jhN8H+v+tsAzWvh3COtKg0H+u0sFbI21P5/jEAMe/NApIo/bKLfYWuWzArTbE+ S7RCSx2Nmzare6c3pZMpDgv1dwCuR40DgZ+dU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=Bzw1Aczj1UYEsMQhGihk4aTfBgfrHWipFjAjgq8sWjvPrY/fMfmFSb57NFIfuoUYZW F/yr9WQsR6/KMaDzxyI470AZj3tWBOVeV/x+jiBS8dw3kZyx5m59fBq2tmu15NO5BicA BPkZszsDJEphV/xBrBxo9Au4ZSNhnsWOnMrj8= MIME-Version: 1.0 Received: by 10.229.98.84 with SMTP id p20mr805584qcn.149.1285209014857; Wed, 22 Sep 2010 19:30:14 -0700 (PDT) Received: by 10.229.212.144 with HTTP; Wed, 22 Sep 2010 19:30:14 -0700 (PDT) In-Reply-To: References: Date: Wed, 22 Sep 2010 19:30:14 -0700 Message-ID: Subject: Re: Compatibility test runs on Sun machine? From: Mamta Satoor To: derby-dev@db.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org I was curious how was DERBY-3644 was discovered. If I understand it right, the results of server start, ping and shutdown for the compatibility test are all done in the org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\testScript.xml which means there is no way to verify if those commands are behaving the way they should be. The rest of the compatibility testing happens in CompatibilityCombinations.java and in problems there are probably caught by that test. By I do not think any problems with start/ping/shutdown done through the testScript.xml will be caught anywhere. Is my understanding correct? thanks, Mamta On Tue, Sep 21, 2010 at 10:30 AM, Knut Anders Hatlen wrote: > Mamta Satoor writes: > >> Hi, >> >> I checked in a fix to DERBY-4786 and the compatibility test for the >> releases I tried ran fine with that change. I was just wondering >> though how often does the compatibility test suite get run on Sun's >> machine? > > It runs daily. Latest results can be found here: > http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/Limited/compatibility_history.html > >> It will be nice to know how they run with my fix for >> DERBY-4786. Also, do have to manually look for the test results >> everytime to see if they ran successfully? Is that how DERBY-3644 was >> detected? > > The results are included in the daily report sent by Ole to > derby-dev. Look for the lines with the label "compatibility" in the > jvm1.6 section. > > -- > Knut Anders >