[
https://issues.apache.org/jira/browse/DERBY-6039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13551004#comment-13551004
]
Knut Anders Hatlen commented on DERBY-6039:
-------------------------------------------
Thanks for looking at the patch, Dag. Committed revision 1431948.
I have no reason to believe there are other ordering bugs, so I don't think we
need to change it to run with fixed execution order now. However, I added some
code to the tearDown() method to print the names of all tables, procedures and
function that live in the APP schema after each test case has completed, and
found that testDuplicates() leaves a procedure called PROCDUP and
testDynamicResultSets() leaves one called INSERTCAUSINGROLLBACK. If other test
cases depend on the existence of those procedures, ordering may affect the
result. I don't know if there are such dependencies, but I think we should make
the two test cases clean up after themselves in any case. I'll post a follow-up
patch.
> Intermittent failure in LangProcedureTest.testDynamicResultSets: Table/View
> 'T1' does not exist.
> ------------------------------------------------------------------------------------------------
>
> Key: DERBY-6039
> URL: https://issues.apache.org/jira/browse/DERBY-6039
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.10.0.0
> Reporter: Knut Anders Hatlen
> Assignee: Knut Anders Hatlen
> Attachments: d6039-1a.diff
>
>
> Seen in the nightly testing:
> http://download.java.net/javadesktop/derby/javadb-5570895-report/javadb-5570895-3573406-details.html
> testDynamicResultSets() needs the table T1, which is created by
> testSqlProcedures(). If testDynamicResultSets() happens to run before
> testSqlProcedures(), it will fail because T1 does not exist.
--
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
