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 "Dag H. Wanvik (Created) (JIRA)" <ji...@apache.org> on 2011/12/09 19:54:41 UTC
[jira] [Created] (DERBY-5529) XATransactionTest: Table/View
'DERBY1016' already exists
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
Reporter: Dag H. Wanvik
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
[jira] [Updated] (DERBY-5529) XATransactionTest: Table/View
'DERBY1016' already exists
Posted by "Jayaram Subramanian (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jayaram Subramanian updated DERBY-5529:
---------------------------------------
Attachment: runoutput5529.out
derby5529.diff
derby5529.stat
Attaching the patch for the issue. Also attaching the log output after the fix.
> 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
> 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
[jira] [Updated] (DERBY-5529) XATransactionTest: Table/View
'DERBY1016' already exists
Posted by "Jayaram Subramanian (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jayaram Subramanian updated DERBY-5529:
---------------------------------------
Issue & fix info: Patch Available
> 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
> 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
[jira] [Updated] (DERBY-5529) XATransactionTest: Table/View
'DERBY1016' already exists
Posted by "Dag H. Wanvik (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik updated DERBY-5529:
---------------------------------
Affects Version/s: 10.9.0.0
> 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
>
> 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
[jira] [Resolved] (DERBY-5529) XATransactionTest: Table/View
'DERBY1016' already exists
Posted by "Knut Anders Hatlen (Resolved) (JIRA)" <ji...@apache.org>.
[ 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