[
https://issues.apache.org/jira/browse/DERBY-5866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13764888#comment-13764888
]
Mamta A. Satoor commented on DERBY-5866:
----------------------------------------
Not sure if this is very helpful, but the last few intermittent failures had
following order of trigger firing sequence
*****************************************
Failure 1
4,NO CASCADE BEFORE,UPDATE,STATEMENT,
13,NO CASCADE BEFORE,UPDATE,ROW,
--wrong
11,NO CASCADE BEFORE,UPDATE,STATEMENT,
18,NO CASCADE BEFORE,UPDATE,ROW,
24,NO CASCADE BEFORE,UPDATE,STATEMENT,
26,NO CASCADE BEFORE,UPDATE,STATEMENT,
29,NO CASCADE BEFORE,UPDATE,ROW,
33,NO CASCADE BEFORE,UPDATE,ROW
*****************************************
Failure 2
1,NO CASCADE BEFORE,DELETE,ROW,
3,NO CASCADE BEFORE,DELETE,ROW,
--wrong
0,NO CASCADE BEFORE,DELETE,STATEMENT,
19,NO CASCADE BEFORE,DELETE,ROW,
22,NO CASCADE BEFORE,DELETE,ROW,
26,NO CASCADE BEFORE,DELETE,ROW,
28,NO CASCADE BEFORE,DELETE,STATEMENT,
*****************************************
Failure 3
1,NO CASCADE BEFORE,UPDATE,ROW,
7,NO CASCADE BEFORE,UPDATE,STATEMENT,
--wrong
14,NO CASCADE BEFORE,UPDATE,STATEMENT,
13,NO CASCADE BEFORE,UPDATE,ROW,
21,NO CASCADE BEFORE,UPDATE,STATEMENT,
25,NO CASCADE BEFORE,UPDATE,ROW,
29,NO CASCADE BEFORE,UPDATE,STATEMENT,
31,NO CASCADE BEFORE,UPDATE,STATEMENT,
*****************************************
Failure 4
2,NO CASCADE BEFORE,INSERT,ROW,
11,NO CASCADE BEFORE,INSERT,STATEMENT,
--wrong
10,NO CASCADE BEFORE,INSERT,STATEMENT,
18,NO CASCADE BEFORE,INSERT,ROW,
20,NO CASCADE BEFORE,INSERT,ROW,
25,NO CASCADE BEFORE,INSERT,STATEMENT,
28,NO CASCADE BEFORE,INSERT,ROW,
29,NO CASCADE BEFORE,INSERT,STATEMENT,
40,NO CASCADE BEFORE,INSERT,STATEMENT,
*****************************************
>
> testFiringConstraintOrder(org.apache.derbyTesting.functionTests.tests.lang.TriggerTest)junit.framework.AssertionFailedError:
> matching triggers need to be fired in order creation:1,NO CASCADE
> BEFORE,DELETE,ROW
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5866
> URL: https://issues.apache.org/jira/browse/DERBY-5866
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.10.1.1, 10.10.1.3
> Environment: Windows IBM 1.6 10.10.0.0 alpha - (1361856)
> Reporter: Kathey Marsden
> Assignee: Mamta A. Satoor
> Labels: derby_triage10_11
> Fix For: 10.8.3.1, 10.9.2.2, 10.10.1.3, 10.11.0.0
>
> Attachments: error-stacktrace.out
>
>
> I saw this failure in the IBM nightlies on 7/15. The subsequent night did not
> fail, so appears intermittent
> http://cloudsoft.usca.ibm.com/intranet/nightlies/derbywinvm/JarResults.2012-07-15/ibm16_suites.All/suites.All.out
> 1)
> testFiringConstraintOrder(org.apache.derbyTesting.functionTests.tests.lang.TriggerTest)junit.framework.AssertionFailedError:
> matching triggers need to be fired in order creation:1,NO CASCADE
> BEFORE,DELETE,ROW
> at
> org.apache.derbyTesting.functionTests.tests.lang.TriggerTest.assertFiringOrder(TriggerTest.java:560)
> at
> org.apache.derbyTesting.functionTests.tests.lang.TriggerTest.testFiringConstraintOrder(TriggerTest.java:500)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
> at
> org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:117)
> at
> org.apache.derbyTesting.junit.BaseJDBCTestCase.runBareOverridable(BaseJDBCTestCase.java:424)
> at
> org.apache.derbyTesting.junit.BaseJDBCTestCase.runBare(BaseJDBCTestCase.java:441)
> 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)
--
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
