[
https://issues.apache.org/jira/browse/DERBY-1764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609231#action_12609231
]
Bryan Pendleton commented on DERBY-1764:
----------------------------------------
The test definitely ran for longer than 3 hours. This morning, it was
still running, 13+ hours after I had started it.
Other than apparently running indefinitely, the test seemed to run
without errors. It printed a lot of innocuous-appearing output to stdout,
lines like:
Tester3 - Run 2157 - Select1 Mon Jun 30 06:41:46 PDT 2008
Tester4 - Run 2233 - Roll1 Mon Jun 30 06:42:06 PDT 2008
Tester3 - Run 2158 - Insert1 Mon Jun 30 06:42:06 PDT 2008
Tester6 - Run 2259 - Roll1 Mon Jun 30 06:42:06 PDT 2008
Tester1 - Run 2271 - CreateA Mon Jun 30 06:42:06 PDT 2008
The command I used to run the test was:
java junit.textui.TestRunner
org.apache.derbyTesting.functionTests.multi.stress.StressMulti
> 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, DERBY-1764-V2.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.
