[
https://issues.apache.org/jira/browse/DERBY-5529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen resolved DERBY-5529.
---------------------------------------
Resolution: Fixed
Fix Version/s: 10.9.0.0
Assignee: Jayaram Subramanian
Issue & fix info: (was: Patch Available)
Thanks, Jayaram. I verified that the test runs cleanly now even if
testForgetExceptionDerby1016NOTA runs before testForgetExceptionDerby1016PROTO.
Committed revision 1213237.
> XATransactionTest: Table/View 'DERBY1016' already exists
> --------------------------------------------------------
>
> Key: DERBY-5529
> URL: https://issues.apache.org/jira/browse/DERBY-5529
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.9.0.0
> Reporter: Dag H. Wanvik
> Assignee: Jayaram Subramanian
> Fix For: 10.9.0.0
>
> Attachments: derby5529.diff, derby5529.stat, runoutput5529.out
>
>
> Cf the test report on trunk.
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.7/testing/Limited/testSummary-1211980.html
> It looks like the ordering between testForgetExceptionDerby1016PROTO and
> testForgetExceptionDerby1016NOTA is inversed in this run on Windows, and the
> test currently requires testForgetExceptionDerby1016PROTO to be run ahead of
> testForgetExceptionDerby1016NOTA. JDK 7 can/will reorder the fixtures.
--
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
