db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-1764) Rewrite stress.multi as a JUnit test
Date Tue, 24 Jun 2008 18:10:45 GMT

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

Kathey Marsden commented on DERBY-1764:

oops. Just tried to run it and got this.
i.TestRunner org.apache.derbyTesting.functionTests.tests.multi.StressMultiTest
testStressMulti Exception in thread "Thread-2" java.lang.NullPointerException
        at org.apache.derbyTesting.functionTests.tests.multi.StressMultiTest.handleException(StressMultiTest.java:234)
        at org.apache.derbyTesting.functionTests.tests.multi.StressMultiTest.access$200(StressMultiTest.java:53)
        at org.apache.derbyTesting.functionTests.tests.multi.StressMultiTest$StressMultiRunnable.run(StressMultiTest.jav
        at java.lang.Thread.run(Thread.java:619)

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