[
https://issues.apache.org/jira/browse/DERBY-1764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12619567#action_12619567
]
Kathey Marsden commented on DERBY-1764:
---------------------------------------
I think we should go ahead and add this test to suites.All and remove
stress.multi runs from derbyall. I think we should leave the stress.multi test
in place so it can be run manually, (not as part of derbyall) for a period of
time while this test stabilizes and so we can be really sure we are testing the
same thing.
One issue with enabling the test is DERBY-3757 which Erlend and I both hit once
running the test. This is a derby bug that might introduce a new intermittent
failure to developer runs of the test. Probably the nightlies won't be
affected since they run with insane builds. I don't think this bug should
prevent us from enabling the test.
Thoughts?
> 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.
