[
https://issues.apache.org/jira/browse/DERBY-1764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615751#action_12615751
]
Kathey Marsden commented on DERBY-1764:
---------------------------------------
I think we should hold off on resolving this issue until the test is
incorporated into the nightlies. I think that the only thing preventing that
now is DERBY-3757. Erlend, could you
1) Reopen this issue.
2) Submit a patch for DERBY-3757 removing the assertion.
3) Submit a patch for this issue adding the test to suites.All and removing it
from derbyall. I'd say lets hold off for a little while on removing the
stress.multi test and all of its supporting files, until the new test has time
to stabilize, but I think we can close this issue as soon as the test is
running in suites.All.
> 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-3a-whitespace_changes.diff,
> derby-1764-derby.log, DERBY-1764-Review.diff, DERBY-1764-V1.diff,
> DERBY-1764-V2.diff, DERBY-1764_4.diff, DERBY-1764_5.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.
