Re: istat-related problems seen in the regression tests

[Rick Hillegas]

On 2/18/11 11:16 AM, Lily Wei wrote:
Hi Rick:
On Fri, Feb 18, 2011 at 7:17 AM, Rick Hillegas 
<rick.hille...@oracle.com <mailto:rick.hille...@oracle.com>> wrote:

    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?

 Yes, it is a intermittent failure and I am still seeing it.

Thanks, Lily. Could you post the stack trace you are seeing on 
DERBY-5030? It surprises me that it is the same stack trace described in 
that bug because generateStatistics() no longer calls 
updateIndexStatsMinion() directly.

Thanks,
-Rick