Sorry about that, I will look and see if there is anything I can do.
I never thought about performance as the additional testing was so
minimal, but as Kathy pointed out the issue is most likely the default
wait time for a lockout tends to be relatively long when compared to
the execution time of tests. I tend to try and alter the default to
make the tests run faster, but probably forgot in this case.
I will look into it.
Ole Solberg wrote:
Knut Anders Hatlen wrote:
"David W. Van Couvering" <[EMAIL PROTECTED]> writes:
I just noticed that in the latest tinderbox run that storetests had an
800% increase in the time it took to run compared to (some baseline?).
I think we should also get an alert email sent when a given suite is
more than 150% (or does someone have a better number) of the baseline.
Comments?
Sorry about that. I just happened to stress test a patch of mine on
the same machine as the tinderbox test was running on.
I have checked the history of 'storetests':
The increase occurs from 2005-12-01 - svn 351569/351543/"Fix for
DERBY-715" which added a new test:"... Added a test that causes 5
deadlocks..."
http://www.multinet.no/~solberg/public/Apache/TinderBox_Derby/UpdateInfo/351569.txt
http://issues.apache.org/jira/browse/DERBY-715
I guess the increase is explained by this.
A comment in the JIRA issue on an expected increase in execution time
for the test would be good though.
