[ 
https://issues.apache.org/jira/browse/DERBY-6704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14110438#comment-14110438
 ] 

Knut Anders Hatlen commented on DERBY-6704:
-------------------------------------------

AutoloadTest failed again on trunk with extended diagnostics. Not on Mac this 
time, but the symptoms are similar (sub-process died with exit code 143). 
http://download.java.net/javadesktop/derby/request_5595117/javadb-task-3919785.html

> 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)

Reply via email to