db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erlend Birkenes (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-1764) Rewrite stress.multi as a JUnit test
Date Mon, 09 Jun 2008 23:09:45 GMT

     [ https://issues.apache.org/jira/browse/DERBY-1764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Erlend Birkenes updated DERBY-1764:
-----------------------------------

    Attachment: DERBY-1764-Review.diff

Here is a preliminary patch for review. It's not complete yet, but the basics works. I've
never done something like this before so I hope it makes sense.
The test runs indefinetely for now, but can be set to break after a certain amount of loops
so that it will eventually pass.. 

I couldn't quite figure out how the weights given to the operations in the old test worked,
so I just spread them out in a similar way, thinking there was no deeper purpose than that.
Let me know if they should be arranged differently.

The old test also prints everything it does in a logfile. Should this test do the same? For
now it prints to stdout, but I'll remove that later.

The only real problem right now is that the threads run for a little while, then stops and
wait for almost exactly 20 seconds then runs for a little while again and keeps going like
that.
It's almost always 20 seconds. I have no idea whats happening, so I need some help with that..

Thats it for now. Please comment.

-Erlend

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


Mime
View raw message