db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6704) Hang in AutoloadTest.spawnProcess:JDBCDriversEmbeddedTest on Mac/jdk7,8
Date Fri, 15 Aug 2014 02:23:19 GMT

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

ASF subversion and git services commented on DERBY-6704:
--------------------------------------------------------

Commit 1618089 from [~dagw] in branch 'code/branches/10.11'
[ https://svn.apache.org/r1618089 ]

DERBY-6704 Hang in AutoloadTest.spawnProcess:JDBCDriversEmbeddedTest on Mac/jdk7,8

Backport of diagnostics patch derby-6704b, svn 1618088.

Patch derby-6704b: it collects std out and err for the spawned
subprocesses, and also forward the debug options "derby.tests.debug"
and "derby.tests.trace" to the subprocesses. If any of those are set,
we collect the std err and std out and print them interleaved with
that of the top process.

The patch will also try to get a jstack status of a hanging subprocess
before killing it (only works on Unixen) - hopefully this would work
also on MacOs; it uses a little dirty reflection to access a private
PID field in the underlying Process class object before trying a
jstack. For this to work, the test must also run using an Oracle JDK,
a JRE doesn't have a jstack.

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

Mime
View raw message