db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5377) AssertionFailedError in testCaseCS4595B_NonUniqueIndex in AccessTest
Date Thu, 15 Mar 2012 19:42:38 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13230463#comment-13230463
] 

Mike Matrigali commented on DERBY-5377:
---------------------------------------

I looked at this and don't understand why the count would be different.  The plan looks right
to me, which is the point of the tests - the key problem the tests were written for was to
insure indexes were being used rather than scans.  I think this is a very minor bug, if it
is a bug at
all, and would welcome someone to fix the test to ignore these counts and we could leave the
bug open if anyone has any ideas on fixing the
underlying problem.  

The kind of bug I was looking for given that correct plan was used was more likely a bug in
the count of pages visits, maybe
some caching of this info in the plan statistics rather than actually visiting different number
of pages.  Again I was never able to reproduce so
never was able to debug it.

These page counts were never meant to be exact to the page, and no application should be counting
on them. 
                
> AssertionFailedError in testCaseCS4595B_NonUniqueIndex in AccessTest
> --------------------------------------------------------------------
>
>                 Key: DERBY-5377
>                 URL: https://issues.apache.org/jira/browse/DERBY-5377
>             Project: Derby
>          Issue Type: Bug
>          Components: Store
>    Affects Versions: 10.8.2.3, 10.9.0.0
>         Environment: Vista, Java 1.5, trunk
>            Reporter: Dag H. Wanvik
>              Labels: derby_triage10_9
>         Attachments: d5377-dump-stats.diff
>
>
> There was 1 failure:
> 1) testCaseCS4595B_NonUniqueIndex(org.apache.derbyTesting.functionTests.tests.store.AccessTest)junit.framework.AssertionFailedError
> 	at org.apache.derbyTesting.functionTests.tests.store.AccessTest.assertStatsOK(AccessTest.java:402)
> 	at org.apache.derbyTesting.functionTests.tests.store.AccessTest.doTestCaseCS4595B(AccessTest.java:1720)
> 	at org.apache.derbyTesting.functionTests.tests.store.AccessTest.testCaseCS4595B_NonUniqueIndex(AccessTest.java:1830)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:112)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
> 	at junit.extensions.TestSetup.run(TestSetup.java:25)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
> 	at junit.extensions.TestSetup.run(TestSetup.java:25)
> 	at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
> 	at junit.extensions.TestSetup.run(TestSetup.java:25)
> Cf. http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.5/testing/Limited/testSummary-1154534.html

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message