db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rick Hillegas <rick.hille...@oracle.com>
Subject re: istat-related problems seen in the regression tests
Date Fri, 18 Feb 2011 15:17:44 GMT
I have logged DERBY-5057 to track an out-of-memory error seen in the 
istat tests on 1.5 during the nightly run last night: 
http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.5/testing/Limited/testSummary-1071310.html

The current roster of known istat-related bugs is:

o DERBY-4940: A placeholder for discussion about and improvements to the 
default istat settings.

o DERBY-5030: May have been fixed by the patch committed on DERBY-5037. 
I didn't see this error in last night's nightly test run. Is anyone 
still seeing this bug? Lily, you mentioned that you had seen it after 
the DERBY-5037 patch was committed. Are you still seeing it?

o DERBY-5038: Extra locks seen in the lock table. Mike has volunteered 
to turn off istat for this test if he feels confident that this won't 
mask some real bug in istat. Mike's activity on this issue is related to 
the email thread linked from DERBY-4940.

o DERBY-5039: Another manifestation of DERBY-5038. Mike's activity 
should cover this one too.

o DERBY-5040: Problems deleting files on Windows platforms. Discussion 
continues on this issue but no-one has claimed responsibility for fixing it.

o DERBY-5045: Assertion failure in UpdateStatisticsTest. No discussion 
or responsible engineer yet.

o DERBY-5057: Out-of-memory error during istat tests.

Thanks,
-Rick


Mime
View raw message