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 7E96411BF4 for ; Tue, 26 Aug 2014 11:11:58 +0000 (UTC) Received: (qmail 53207 invoked by uid 500); 26 Aug 2014 11:11:58 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 53184 invoked by uid 500); 26 Aug 2014 11:11:58 -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 53173 invoked by uid 99); 26 Aug 2014 11:11:58 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Aug 2014 11:11:58 +0000 Date: Tue, 26 Aug 2014 11:11:58 +0000 (UTC) From: "Knut Anders Hatlen (JIRA)" To: derby-dev@db.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (DERBY-6704) Hang in AutoloadTest.spawnProcess:JDBCDriversEmbeddedTest on Mac/jdk7,8 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DERBY-6704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14110606#comment-14110606 ] Knut Anders Hatlen commented on DERBY-6704: ------------------------------------------- The latest failure may be a red herring. RuntimeInfoTest had failed earlier in the test run (DERBY-6714). AutoloadTest seems to be waiting for the server port to become available. RuntimeInfoTest is supposed to shut down its server instance manually, but the failure happens just before it gets to the shutdown code, so there is a possibility that it's the server from that test that's blocking AutoloadTest. > Hang in AutoloadTest.spawnProcess:JDBCDriversEmbeddedTest on Mac/jdk7,8 > ----------------------------------------------------------------------- > > Key: DERBY-6704 > URL: https://issues.apache.org/jira/browse/DERBY-6704 > Project: Derby > Issue Type: Bug > Reporter: Dag H. Wanvik > Attachments: derby-6704-01-aa-cleanupJavadocWarnings.diff, derby-6704.diff, derby-6704b.diff, derby-6704b.status > > > In our release tests for 10.11 we have seen this stack trace: > {code} > org.apache.derbyTesting.functionTests.tests.jdbcapi.AutoloadTest.spawnProcess:JDBCDriversEmbeddedTest 2701.548 s > junit.framework.AssertionFailedError: Test process failed:Spawned org.apache.derbyTesting.functionTests.tests.jdbcapi.JDBCDriversEmbeddedTest exitCode=143 > STDOUT: > .. > at org.apache.derbyTesting.functionTests.tests.jdbcapi.AutoloadTest.spawnProcess(AutoloadTest.java:256) > at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:118) > at org.apache.derbyTesting.junit.BaseJDBCTestCase.runBareOverridable(BaseJDBCTestCase.java:440) > at org.apache.derbyTesting.junit.BaseJDBCTestCase.runBare(BaseJDBCTestCase.java:457) > at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) > at junit.extensions.TestSetup$1.protect(TestSetup.java:21) > at junit.extensions.TestSetup.run(TestSetup.java:25) > {code} > presumably because the spawned process is killed by the test framework; it had been executing for 2701 second, but we don't have much insight into what happened to the subprocess because we don't collect its std our or std err. -- This message was sent by Atlassian JIRA (v6.2#6252)