[DERBY-6450] dblook_test_territory nightly test failure

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 10.11.1.1
• Component/s: SQL

Environment

------------------ Java Information ------------------
Java Version: 1.6.0
Java Vendor: IBM Corporation
Java home: C:\jartest\ibm16\jre
Java classpath: C:/jartest/jars/derbyrun.jar;C:/jartest/jars/derbyTesting.jar;c:/jartest/tools/java/jakarta-oro-2.0.8.jar;c:/jartest/junit/junit.jar;
OS name: Windows Server 2008 R2
OS architecture: x86
OS version: 6.1 build 7601 Service Pack 1
Java user name: cloudtest
Java user home: C:\Users\cloudtest
Java user dir: C:\jartest\JarResults.2013-12-27\ibm16_derbyall
java.specification.name: Java Platform API Specification
java.specification.version: 1.6
java.runtime.version: pwi3260sr15-20131017_01 (SR15)
java.fullversion: JRE 1.6.0 IBM J9 2.4 Windows Server 2008 R2 x86-32 jvmwi3260sr15-20131016_170922 (JIT enabled, AOT enabled)
J9VM - 20131016_170922
JIT - r9_20130920_46510ifx2
GC - GA24_Java6_SR15_20131016_1337_B170922
--------- Derby Information --------

• Bug behavior facts: Regression Test Failure
• Assignee: Unassigned
• Reporter: Mike Matrigali
• Created: 08/Jan/14 19:29
• Updated: 09/Jan/14 10:12
• Resolved: 09/Jan/14 10:12

Description

Failure Details:

• • • • • • • • • Diff file derbyall/derbynetclientmats/DerbyNetClient/encodingTests/TestEnc.diff
    • Start: TestEnc jdk1.6.0 DerbyNetClient derbynetclientmats:encodingTests 2013-12-27 19:56:12 ***
      derbyTesting.encoding can only be used with jdk15, skipping test
    • End: TestEnc jdk1.6.0 DerbyNetClient derbynetclientmats:encodingTests 2013-12-27 19:56:12 ***
      • • • • • • Diff file derbyall/derbytools/dblook_test_territory.diff
    • Start: dblook_test_territory jdk1.6.0 derbyall:derbytools 2013-12-27 19:55:53 ***
      6538a6539
      > CREATE TRIGGER "APP"."TR16" AFTER UPDATE ON "APP"."T1" REFERENCING NEW_TABLE AS NEW FOR EACH STATEMENT select * from sys.systables natural join sys.sysschemas where exists(select * from new where x > 100)
      6540d6540
      < CREATE TRIGGER "APP"."TR16" AFTER UPDATE ON "APP"."T1" REFERENCING NEW_TABLE AS NEW FOR EACH STATEMENT select * from sys.systables natural join sys.sysschemas where exists(select * from new where x > 100)
      6544a6545
      > CREATE TRIGGER "APP"."TR22" AFTER UPDATE ON "APP"."T1" REFERENCING NEW_TABLE AS NEW FOR EACH STATEMENT select * from sys.systables natural join sys.sysschemas where exists(select * from new where x > 100)
      6546d6546
      < CREATE TRIGGER "APP"."TR22" AFTER UPDATE ON "APP"."T1" REFERENCING NEW_TABLE AS NEW FOR EACH STATEMENT select * from sys.systables natural join sys.sysschemas where exists(select * from new where x > 100)
      Test Failed.
    • End: dblook_test_territory jdk1.6.0 derbyall:derbytools 2013-12-27 19:56:09 ***

Issue Links

• duplicates: DERBY-5866 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
• relates to: DERBY-6387 Incorrect ordering of triggers in dblook