db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erlend Birkenes" <erl...@birkenes.net>
Subject Re: [jira] Commented: (DERBY-1764) Rewrite stress.multi as a JUnit test
Date Mon, 30 Jun 2008 17:13:22 GMT
Hi Bryan. Thanks for trying it again :)

The test definitely ran for longer than 3 hours. This morning, it was
> still running, 13+ hours after I had started it.
>

Weird..what kind of system are you running it on. I run on Ubuntu 8.04 and
have tested it with Sun jvm 1.4, 5 and 6.
The test uses System.currentTimeMillis() to calculate time, like this:

runtime = minutes*60*1000;
...
if ((starttime + runtime) <= System.currentTimeMillis()) {
    println(name + " - STOPPING - " + new
Date(System.currentTimeMillis()).toString());
    break;
}

Is there any reason why this might not work?


>
> Other than apparently running indefinitely, the test seemed to run
> without errors. It printed a lot of innocuous-appearing output to stdout,
> lines like:
>
> Tester3 - Run 2157 - Select1 Mon Jun 30 06:41:46 PDT 2008
> Tester4 - Run 2233 - Roll1 Mon Jun 30 06:42:06 PDT 2008
> Tester3 - Run 2158 - Insert1 Mon Jun 30 06:42:06 PDT 2008
> Tester6 - Run 2259 - Roll1 Mon Jun 30 06:42:06 PDT 2008
> Tester1 - Run 2271 - CreateA Mon Jun 30 06:42:06 PDT 2008
>

It should not print to stdout unless you enable verbose or turn on the DEBUG
boolean in the source (which does the same thing..)
Also it seems like you have 20 second deadlock timeout between the two first
lines there, and that should be 3 sec.
So there seems to be some problem with the system properties.. I have no
idea what.


>
> The command I used to run the test was:
>
> java junit.textui.TestRunner
> org.apache.derbyTesting.functionTests.multi.stress.StressMulti
>

This is wrong. You probably mean
org.apache.derbyTesting.functionTests.tests.multi.StressMultiTest?


Can someone else please test this so we get more info?

-Erlend

Mime
View raw message