You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <ji...@apache.org> on 2013/02/15 17:15:14 UTC
[jira] [Updated] (DERBY-6073) Test ordering instability in
StatementPoolingTest
[ https://issues.apache.org/jira/browse/DERBY-6073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas updated DERBY-6073:
---------------------------------
Attachment: z.diff
Attaching z.diff. After applying this patch, I see the error on trunk. I also see the error after applying the patch to 10.9 and then running with Java 6 or Java 7. Because the problem can be reproduced on 10.9, I do not believe this is a regression introduced by work on the trunk.
> Test ordering instability in StatementPoolingTest
> -------------------------------------------------
>
> Key: DERBY-6073
> URL: https://issues.apache.org/jira/browse/DERBY-6073
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.9.1.0, 10.10.0.0
> Environment: Java 7, Java 8
> Reporter: Rick Hillegas
> Attachments: z.diff
>
>
> StatementPoolingTest.testPoolingEnabledByCheckingImplementationDetails() assumes that the client-side statement cache will have been primed by a previous test case, testCacheOverflow(). On Java 7 and Java 8 the test order is not deterministic. If testPoolingEnabledByCheckingImplementationDetails() is the first test case to run, then it fails with this error:
> org.apache.derbyTesting.functionTests.tests.jdbcapi.StatementPoolingTest.assertClassName(StatementPoolingTest.java:147)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.StatementPoolingTest.testPoolingEnabledByCheckingImplementationDetails(StatementPoolingTest.java:89)
> I will attach a patch which forces testPoolingEnabledByCheckingImplementationDetails() to be first in the test order. With this patch, StatementPoolingTest fails for me on Java 7 when run on the 10.9 branch as well as on trunk.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira