db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-6073) Test ordering instability in StatementPoolingTest
Date Fri, 15 Feb 2013 17:25:13 GMT

     [ https://issues.apache.org/jira/browse/DERBY-6073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rick Hillegas updated DERBY-6073:
---------------------------------

    Attachment: derby-6073-02-aa-java8tweak.diff

Attaching derby-6073-02-aa-java8tweak.diff. This patch adjusts the assertClassName() method
to account for the fact that some *40 classes have corresponding *42 subclasses and some don't.
 Committed at subversion revision 1446698.

The logic is brittle and will probably break again when we implement the next (Java 9) rev
of JDBC. But maybe we can just kick the can down the road for another two years. I will unassign
myself from this bug so that others can improve this bug fix if they want to.

Touches the following file:

M       java/testing/org/apache/derbyTesting/functionTests/tests/jdbcapi/StatementPoolingTest.java

                
> 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
>            Assignee: Rick Hillegas
>         Attachments: derby-6073-01-aa-fixTestCaseOrder.diff, derby-6073-02-aa-java8tweak.diff,
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

Mime
View raw message