Return-Path: X-Original-To: apmail-db-derby-dev-archive@www.apache.org Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2BBC1E94E for ; Thu, 28 Feb 2013 21:32:03 +0000 (UTC) Received: (qmail 25240 invoked by uid 500); 28 Feb 2013 21:32:03 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 25188 invoked by uid 500); 28 Feb 2013 21:32:03 -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 25181 invoked by uid 99); 28 Feb 2013 21:32:02 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Feb 2013 21:32:02 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of msatoor@gmail.com designates 209.85.212.181 as permitted sender) Received: from [209.85.212.181] (HELO mail-wi0-f181.google.com) (209.85.212.181) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Feb 2013 21:31:56 +0000 Received: by mail-wi0-f181.google.com with SMTP id hm6so2711990wib.8 for ; Thu, 28 Feb 2013 13:31:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=T5pKxDQLkpCrwFNRTd59ToIUIUhEOSLH33jrDYToeWE=; b=hqcHYHR418hwAtbHehgflOgy5OUXGJgJsuhaEF2ty5Lkyzg/anJLSFHMcxWt0GlpOc D/I59XAKPXmuNf953/M0sgpTFBoT2HLbtQ3dqXywVZwDvGuvG81565QgxrwruUL6WJOC ON/7skCuOFQYAGYr8CdWTaSbH1wzMaEn/sh8B4kHRHjBisdS1mXNZTvVsTcxDj7T/fYf al4bF88+sor/dqBGhzFPWt6iTAhmpGEA3kTyFUeRrO/nKltyHHwsuq8QbuW6gx782QlM I4F+XLhmQ0m7fDpVXQNgvzX1pLlbG+OMh7XS7bDhfUlVfvbDqbTGcCDwtnx9erUZVd1g RO9A== MIME-Version: 1.0 X-Received: by 10.180.78.35 with SMTP id y3mr206259wiw.22.1362087096750; Thu, 28 Feb 2013 13:31:36 -0800 (PST) Received: by 10.216.232.163 with HTTP; Thu, 28 Feb 2013 13:31:36 -0800 (PST) In-Reply-To: <512FA6C1.4010409@oracle.com> References: <201302281021.r1SALIIw022986@ucsinet21.oracle.com> <512FA6C1.4010409@oracle.com> Date: Thu, 28 Feb 2013 13:31:36 -0800 Message-ID: Subject: Re: [Java DB - testing] Error continuous 10.9 (rev 1451023) 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 Hi Rick, Thanks for conforming that this could be an environmental problem. I will go ahead and backport my changes to 10.8 since 10.9 seems to have run the tests fine with the backport. I will also go ahead and close the jira DERBY-6095 which was opened for failing tests. thanks, Mamta On Thu, Feb 28, 2013 at 10:49 AM, Rick Hillegas wrote: > On 2/28/13 8:38 AM, Mamta Satoor wrote: >> >> As per "Test report: >> http://download.java.net/javadesktop/derby/javadb-5573355-report/" >> (http://download.java.net/javadesktop/derby/javadb-5573355-report/%27), >> the exceptions with amd64_jdk7 are for junit tests in >> org.apache.derbyTesting.functionTests.tests.management and they all >> seem to be as follows >> >> java.rmi.ConnectException: Connection refused to host: 10.163.184.120; >> nested exception is: >> java.net.ConnectException: Connection timed out" >> >> Could this be a machine issue? I can do a dummy checkin into 10.9 by >> adding some comment into the code which will fire the tests again on >> 10.9(it looks like Sun's machine will fire a 10.9 run only if there is >> a checkin on that codeline). >> >> I will also file a jira for this. >> >> thanks, >> Mamta >> >>> I see that after my backport for DERBY-6053 into 10.9, number of junit >>> tests(50) have failed with amd64_jdk7 on 10.9 codeline. Interestingly, >>> the tests passed with ia32_jdk5 and ia32_jdk6. They also passed with >>> ibm1.7 on my machine before the checkin so I am not sure what is the >>> reason behind the failures with amd64_jdk7. I am looking into it. >>> >>> thanks, >>> Mamta >>> >>> On Thu, Feb 28, 2013 at 2:21 AM, wrote: >>>> >>>> Java DB testing and reporting infrastructure. >>>> >>>> Error continuous 10.9 (rev 1451023) >>>> >>>> 50 errors. >>>> >>>> Test report: >>>> http://download.java.net/javadesktop/derby/javadb-5573355-report/ > > Hi Mamta, > > This looks like an environmental problem in the Oracle test lab which runs > these tests. A subsequent test run (triggered by a later checkin) appears to > have run cleanly. The instability in the test lab needs to be addressed. I'm > afraid I can't tell you when the lab will stabilize. > > Thanks, > -Rick