db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-1764) Rewrite stress.multi as a JUnit test
Date Mon, 07 Jul 2008 07:09:31 GMT

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

Knut Anders Hatlen commented on DERBY-1764:

> 2) Need to add functionality so that if threads hang and cannot
> finish on their own, we dump the stack traces and interrupt the
> threads. I think this is important as when we have had failures in
> this test in the past, we have seen the threads hang.

Perhaps it better to let it hang? One can always get the stack traces
with kill -QUIT or jstack when the hang happens, and one can also
attach a debugger to the process to see what's going on. Interrupting
the test may prevent cleanup code from being executed or leave the
engine in a bad state, which can cause subsequent errors and make the
problem harder to debug.

> Rewrite stress.multi as a JUnit test
> ------------------------------------
>                 Key: DERBY-1764
>                 URL: https://issues.apache.org/jira/browse/DERBY-1764
>             Project: Derby
>          Issue Type: Test
>          Components: Test
>            Reporter: Knut Anders Hatlen
>            Assignee: Erlend Birkenes
>         Attachments: derby-1764-derby.log, DERBY-1764-Review.diff, DERBY-1764-V1.diff,
> Currently, stress.multi consists of a number of sql scripts that are run in ij. It often
fails with cryptic error messages, and since it uses ij, there is often no stack trace. It
would be very useful to rewrite the test in JUnit so that we can get better error messages
and stack traces when it fails.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message