db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-1764) Rewrite stress.multi as a JUnit test
Date Mon, 08 Sep 2008 18:17:44 GMT

     [ 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_use_System_PropertySetup_diff.txt

I think I am going to back out the change to enable the test. I will do that as soon as suites.All
finishes.  

I attempted to change the test to use SystemPropertyTestSetup but am having some problems.
If I run with derby.tests.debug=true, I see longer delays than the 2 or 3 seconds we have
set for lock timeout and deadlock timeout.  I am attaching the diff and would appreciate any
input on why this is not working.


> 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_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.


Mime
View raw message