Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 72877 invoked from network); 2 Mar 2006 19:13:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 2 Mar 2006 19:13:09 -0000 Received: (qmail 35518 invoked by uid 500); 2 Mar 2006 19:13:53 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 35406 invoked by uid 500); 2 Mar 2006 19:13:53 -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 35305 invoked by uid 99); 2 Mar 2006 19:13:53 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Mar 2006 11:13:53 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= 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; Thu, 02 Mar 2006 11:13:51 -0800 Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234]) by e4.ny.us.ibm.com (8.12.11/8.12.11) with ESMTP id k22JDTpq017275 for ; Thu, 2 Mar 2006 14:13:29 -0500 Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by d01relay02.pok.ibm.com (8.12.10/NCO/VER6.8) with ESMTP id k22JDTGJ128478 for ; Thu, 2 Mar 2006 14:13:29 -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 k22JDT4k029782 for ; Thu, 2 Mar 2006 14:13:29 -0500 Received: from [127.0.0.1] (sig-9-48-110-131.mts.ibm.com [9.48.110.131]) by d01av03.pok.ibm.com (8.12.11/8.12.11) with ESMTP id k22JDL2M029378 for ; Thu, 2 Mar 2006 14:13:28 -0500 Message-ID: <440743CC.70107@apache.org> Date: Thu, 02 Mar 2006 11:13:16 -0800 From: Daniel John Debrunner User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en-us, en, de MIME-Version: 1.0 To: derby-dev@db.apache.org Subject: Re: [jira] Commented: (DERBY-999) test SURTest.junit fails with ibm142 References: <151486616.1141323522126.JavaMail.jira@ajax.apache.org> <44074056.3010202@sbcglobal.net> In-Reply-To: <44074056.3010202@sbcglobal.net> X-Enigmail-Version: 0.90.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii 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 Mike Matrigali wrote: > New tests that break regression suite should be backed out of suite. This case is interesting because the test does "pass" on Sun's jdk 1.4.2, that I think is reasonable for test that truly passes to be an addition to the derbyall regression suite. [ Assuming of course the test is not intentionally written to only run on a single jvm. ] Now if a valid test fails on IBM's 1.4.2, that's a problem for whoever has the itch for derby to run on that vm, same as if the test failed on Jrockit. But in this case, the test is actually failing, but running clean since the failures are in the master file. Since the failures are not expected in the long run, I assume not a lot of work has gone into making the failure output consistent across jvms. I'm not sure what should be done about this. Seems to be wait for the patch that implements the functionality or remove it from the suites. I know that it wastes my time, having this consistent failure in my runs, also conditions me to ignore that test in the future. If I'm breaking that in some way, and don't realize it's meant to run clean, then I'm going to ignore it's error and checkin a bad fix. I just added a test that I knew showed an error (AggregateClassLoading.java) but didn't add it to the suites until I had the fix, seemed more natural to me. Makes the test available for others to use, doesn't break anyone. Dan.