[
https://issues.apache.org/jira/browse/DERBY-1764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-1764:
----------------------------------
Attachment: DERBY-1764_sysprops_diff.txt
Attached is a patch that enables the test and uses SystemPropertiesTestSetup
for setting the system properties for embedded. I added a staticproperties
flag to SystemPropertiesTestSetup that will cause the engine to shutdown on
setup and teardown so that the properties take effect. It is still not
perfect but I would like to check it in as an incremental improvement. The
SystemPropertyTestSetup works fine for the embedded test but not for network
server because it causes protocol errors and not for encrypted because the
database cannot booted after it has been shutdown. So I did the
SystemPropertiesTestSetup only for embedded.
Another problem is that the database will get deleted after the test run, so
the property to keep the transaction log is really not that useful. I plan to
change BaseTestCase to save off the database if the test fails. I'll open up
another issue for that change.
I ran suites.All (hit only DERBY-3719) , StressMutli10x1,StressMulti50x59
> 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,
> DERBY-1764_8_Use_DatabasePropertiesTestSetup.diff,
> DERBY-1764_sysprops_diff.txt, derby-1764_use_System_PropertySetup_diff.txt
>
>
> 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.
