[
https://issues.apache.org/jira/browse/DERBY-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lily Wei updated DERBY-5103:
----------------------------
Attachment: rjall.out
I ran this test on Windows 7 on Java 7 build 132. I saw this same stack trace
on my machine:
4) testTriggerContainsSql(org.apache.derbyTesting.functionTests.tests.lang.Proce
dureInTriggerTest)junit.framework.AssertionFailedError: expected:<2> but was:<4>
at org.apache.derbyTesting.functionTests.tests.lang.ProcedureInTriggerTe
st.checkAndResetGetConnectionProcCount(ProcedureInTriggerTest.java:514)
at org.apache.derbyTesting.functionTests.tests.lang.ProcedureInTriggerTe
st.testTriggerContainsSql(ProcedureInTriggerTest.java:120)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:43)
at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:
112)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57
)
I am attaching my output rjall.out here.
> ProcedureInTriggerTest depends on implicit ordering of test cases
> -----------------------------------------------------------------
>
> Key: DERBY-5103
> URL: https://issues.apache.org/jira/browse/DERBY-5103
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.8.0.0
> Reporter: Knut Anders Hatlen
> Attachments: rjall.out
>
>
> If for example the test case testTriggerContainsSql is executed as the first
> test case, it will fail with the following error:
> 1)
> testTriggerContainsSql(org.apache.derbyTesting.functionTests.tests.lang.ProcedureInTriggerTest)junit.framework.AssertionFailedError:
> expected:<2> but was:<0>
> at
> org.apache.derbyTesting.functionTests.tests.lang.ProcedureInTriggerTest.checkAndResetGetConnectionProcCount(ProcedureInTriggerTest.java:514)
> at
> org.apache.derbyTesting.functionTests.tests.lang.ProcedureInTriggerTest.testTriggerContainsSql(ProcedureInTriggerTest.java:120)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at
> org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:112)
> at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
> at junit.extensions.TestSetup.run(TestSetup.java:25)
> at
> org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
> The test should either make the order of the test cases explicit or make the
> test cases independent of the order in which they run.
> Seen in the nightly tests, for example here:
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.7/testing/testlog/lin/1076682-suitesAll_diff.txt
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
