[
https://issues.apache.org/jira/browse/DERBY-1764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12629163#action_12629163
]
Knut Anders Hatlen commented on DERBY-1764:
-------------------------------------------
The tinderbox failed after StressMultiTest was added to suites.AllPackages.
http://dbtg.thresher.com/derby/test/tinderbox_trunk16/jvm1.6/testing/Limited/testSummary-692494.html
I think the problem may be that StressMultiTest sets a number of system
properties in its suite() method. Since all the suite() methods are run before
any of the tests, these properties will be used by all the tests in suites.All.
To set system properties, SystemPropertiesTestSetup should be used instead.
> 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, DERBY-1764_6.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.
