[jira] [Commented] (DERBY-6881) Test failures with JDK 9-ea b111
[ https://issues.apache.org/jira/browse/DERBY-6881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15218981#comment-15218981 ] Bryan Pendleton commented on DERBY-6881: Thanks for digging into this Knut Anders. I eyeballed both patches and they look great to me. For the benefit of those of us still learning the "new" Java, can you break this line down in a bit more detail: PrivilegedAction pa = () -> new URLClassLoader(new URL[0]); I'm just trying to improve my reading skills, and am uncertain about what I'm seeing. > Test failures with JDK 9-ea b111 > > > Key: DERBY-6881 > URL: https://issues.apache.org/jira/browse/DERBY-6881 > Project: Derby > Issue Type: Bug > Components: Test >Affects Versions: 10.13.0.0 >Reporter: Knut Anders Hatlen > Attachments: d6881-classloader.diff, d6881-sed.diff > > > With JDK 9-ea b111 there are a number of test failures. > Tests that use ClassLoaderTestSetup fail because the context class loader no > longer is a URLClassLoader, which causes a ClassCastException in the class > loader magic performed by the test setup: > {noformat} > java.lang.ClassCastException: jdk.internal.loader.ClassLoaders$AppClassLoader > (in module: java.base) cannot be cast to java.net.URLClassLoader (in module: > java.base) > at > org.apache.derbyTesting.junit.ClassLoaderTestSetup$1.run(ClassLoaderTestSetup.java:53) > at > org.apache.derbyTesting.junit.ClassLoaderTestSetup$1.run(ClassLoaderTestSetup.java:50) > at java.security.AccessController.doPrivileged(java.base@9-ea/Native > Method) > at > org.apache.derbyTesting.junit.ClassLoaderTestSetup.makeClassLoader(ClassLoaderTestSetup.java:49) > at > org.apache.derbyTesting.junit.ClassLoaderTestSetup.setUp(ClassLoaderTestSetup.java:64) > at junit.extensions.TestSetup$1.protect(TestSetup.java:20) > at junit.extensions.TestSetup.run(TestSetup.java:25) > at > org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:58) > {noformat} > CollationTest, CollationTest2, LocalizedAttributeScriptTest and > LocalizedDisplayScriptTest have failures, for example: > {noformat} > junit.framework.AssertionFailedError: Column value mismatch @ column 'ID', > row 1: > Expected: >4< > Found:>6< > ID,NAME > -- >[6, aacorn] >[4, Acorn] >[2, Ącorn] >[0, Smith] >[5, Śmith] >[1, Zebra] >[3, Żebra] > at > org.apache.derbyTesting.junit.BaseTestCase.newAssertionFailedError(BaseTestCase.java:1177) > at org.apache.derbyTesting.junit.JDBC.addRsToReport(JDBC.java:1998) > at > org.apache.derbyTesting.junit.JDBC.assertRowInResultSet(JDBC.java:1497) > at > org.apache.derbyTesting.junit.JDBC.assertRowInResultSet(JDBC.java:1395) > at > org.apache.derbyTesting.junit.JDBC.assertFullResultSetMinion(JDBC.java:1257) > at > org.apache.derbyTesting.junit.JDBC.assertFullResultSet(JDBC.java:1168) > at > org.apache.derbyTesting.junit.JDBC.assertFullResultSet(JDBC.java:1125) > at > org.apache.derbyTesting.junit.JDBC.assertFullResultSet(JDBC.java:1083) > at > org.apache.derbyTesting.functionTests.tests.lang.CollationTest.checkLangBasedQuery(CollationTest.java:2055) > at > org.apache.derbyTesting.functionTests.tests.lang.CollationTest.testNorwayCollation(CollationTest.java:482) > at > org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:120) > at > org.apache.derbyTesting.junit.BaseJDBCTestCase.runBareOverridable(BaseJDBCTestCase.java:443) > at > org.apache.derbyTesting.junit.BaseJDBCTestCase.runBare(BaseJDBCTestCase.java:460) > 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 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:58) > 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) > Caused by: junit.framework.AssertionFailedError: Column value mismatch @ > column 'ID', row 1: > Expected: >4< > Found:>6< > at > org.apache.derbyTesting.junit.JDBC.assertRowInResultSet(JDBC.java:1492) > {noformat} > And the stack trace deletion patterns in the Sed class seem to be missing out > on some stack frames now, causing failures like this one in dblook_test and > dblook_test_territory: > {noformat} > * Diff file derbyall/de
[jira] [Updated] (DERBY-6881) Test failures with JDK 9-ea b111
[ https://issues.apache.org/jira/browse/DERBY-6881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Knut Anders Hatlen updated DERBY-6881: -- Attachment: d6881-sed.diff Attaching another patch, d6881-sed.diff, which fixes the failures in the dblook tests. It updates the Sed class to recognize both the old format and the new format of stack traces. Specifically, the stack traces used to contain a line that looked like this: at java.io.FileInputStream.open0(Native Method) With the latest build of JDK 9-ea, it has changed to this: at java.io.FileInputStream.open0(java.base@9-ea/Native Method) The regular expression that recognized the former, has been updated to also recognize the latter. > Test failures with JDK 9-ea b111 > > > Key: DERBY-6881 > URL: https://issues.apache.org/jira/browse/DERBY-6881 > Project: Derby > Issue Type: Bug > Components: Test >Affects Versions: 10.13.0.0 >Reporter: Knut Anders Hatlen > Attachments: d6881-classloader.diff, d6881-sed.diff > > > With JDK 9-ea b111 there are a number of test failures. > Tests that use ClassLoaderTestSetup fail because the context class loader no > longer is a URLClassLoader, which causes a ClassCastException in the class > loader magic performed by the test setup: > {noformat} > java.lang.ClassCastException: jdk.internal.loader.ClassLoaders$AppClassLoader > (in module: java.base) cannot be cast to java.net.URLClassLoader (in module: > java.base) > at > org.apache.derbyTesting.junit.ClassLoaderTestSetup$1.run(ClassLoaderTestSetup.java:53) > at > org.apache.derbyTesting.junit.ClassLoaderTestSetup$1.run(ClassLoaderTestSetup.java:50) > at java.security.AccessController.doPrivileged(java.base@9-ea/Native > Method) > at > org.apache.derbyTesting.junit.ClassLoaderTestSetup.makeClassLoader(ClassLoaderTestSetup.java:49) > at > org.apache.derbyTesting.junit.ClassLoaderTestSetup.setUp(ClassLoaderTestSetup.java:64) > at junit.extensions.TestSetup$1.protect(TestSetup.java:20) > at junit.extensions.TestSetup.run(TestSetup.java:25) > at > org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:58) > {noformat} > CollationTest, CollationTest2, LocalizedAttributeScriptTest and > LocalizedDisplayScriptTest have failures, for example: > {noformat} > junit.framework.AssertionFailedError: Column value mismatch @ column 'ID', > row 1: > Expected: >4< > Found:>6< > ID,NAME > -- >[6, aacorn] >[4, Acorn] >[2, Ącorn] >[0, Smith] >[5, Śmith] >[1, Zebra] >[3, Żebra] > at > org.apache.derbyTesting.junit.BaseTestCase.newAssertionFailedError(BaseTestCase.java:1177) > at org.apache.derbyTesting.junit.JDBC.addRsToReport(JDBC.java:1998) > at > org.apache.derbyTesting.junit.JDBC.assertRowInResultSet(JDBC.java:1497) > at > org.apache.derbyTesting.junit.JDBC.assertRowInResultSet(JDBC.java:1395) > at > org.apache.derbyTesting.junit.JDBC.assertFullResultSetMinion(JDBC.java:1257) > at > org.apache.derbyTesting.junit.JDBC.assertFullResultSet(JDBC.java:1168) > at > org.apache.derbyTesting.junit.JDBC.assertFullResultSet(JDBC.java:1125) > at > org.apache.derbyTesting.junit.JDBC.assertFullResultSet(JDBC.java:1083) > at > org.apache.derbyTesting.functionTests.tests.lang.CollationTest.checkLangBasedQuery(CollationTest.java:2055) > at > org.apache.derbyTesting.functionTests.tests.lang.CollationTest.testNorwayCollation(CollationTest.java:482) > at > org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:120) > at > org.apache.derbyTesting.junit.BaseJDBCTestCase.runBareOverridable(BaseJDBCTestCase.java:443) > at > org.apache.derbyTesting.junit.BaseJDBCTestCase.runBare(BaseJDBCTestCase.java:460) > 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 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:58) > 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) > Caused by: junit.framework.AssertionFailedError: Column value mismatch @ > column 'ID', row 1: > Expected: >4< > Found:>6< > at > org.apache.derbyTesting.junit.JDBC.assertRowInResultSet(JDBC.java:1492) > {noformat} > And the stack trace deletion patterns in the Sed class seem to be missing ou
[jira] [Updated] (DERBY-6881) Test failures with JDK 9-ea b111
[ https://issues.apache.org/jira/browse/DERBY-6881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Knut Anders Hatlen updated DERBY-6881: -- Attachment: d6881-classloader.diff The attached patch, d6881-classloader.diff, seems to fix the problem with ClassLoaderTestSetup. The purpose of ClassLoaderTestSetup is to make a test case run with a non-default context class loader. It is only used by one test case, in SecureServerTest to test the fix for the class loader leak in DERBY-6619. The way it does this currently, is by cloning the original context class loader, which happens to be the application class loader. As http://openjdk.java.net/jeps/261 explains, the application class loader is a URLClassLoader from Java 1.2 to Java 8, but it is some internal class in Java 9. When ClassLoaderTestSetup casts it to URLClassLoader, it consequently throws a ClassCastException with Java 9. It turns out that the new context class loader does not need to be a clone of the original class loader for the purpose of this test. It seems to be sufficient that it is some other class loader than the system class loader in order to exercise the code path we want to test. The patch therefore changes ClassLoaderTestSetup to create an empty URLClassLoader that wraps the system class loader. This way we avoid the unreliable cast that causes problems on Java 9. SecureServerTest passes both on Java 8 and Java 9-ea b111 with this patch. > Test failures with JDK 9-ea b111 > > > Key: DERBY-6881 > URL: https://issues.apache.org/jira/browse/DERBY-6881 > Project: Derby > Issue Type: Bug > Components: Test >Affects Versions: 10.13.0.0 >Reporter: Knut Anders Hatlen > Attachments: d6881-classloader.diff > > > With JDK 9-ea b111 there are a number of test failures. > Tests that use ClassLoaderTestSetup fail because the context class loader no > longer is a URLClassLoader, which causes a ClassCastException in the class > loader magic performed by the test setup: > {noformat} > java.lang.ClassCastException: jdk.internal.loader.ClassLoaders$AppClassLoader > (in module: java.base) cannot be cast to java.net.URLClassLoader (in module: > java.base) > at > org.apache.derbyTesting.junit.ClassLoaderTestSetup$1.run(ClassLoaderTestSetup.java:53) > at > org.apache.derbyTesting.junit.ClassLoaderTestSetup$1.run(ClassLoaderTestSetup.java:50) > at java.security.AccessController.doPrivileged(java.base@9-ea/Native > Method) > at > org.apache.derbyTesting.junit.ClassLoaderTestSetup.makeClassLoader(ClassLoaderTestSetup.java:49) > at > org.apache.derbyTesting.junit.ClassLoaderTestSetup.setUp(ClassLoaderTestSetup.java:64) > at junit.extensions.TestSetup$1.protect(TestSetup.java:20) > at junit.extensions.TestSetup.run(TestSetup.java:25) > at > org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:58) > {noformat} > CollationTest, CollationTest2, LocalizedAttributeScriptTest and > LocalizedDisplayScriptTest have failures, for example: > {noformat} > junit.framework.AssertionFailedError: Column value mismatch @ column 'ID', > row 1: > Expected: >4< > Found:>6< > ID,NAME > -- >[6, aacorn] >[4, Acorn] >[2, Ącorn] >[0, Smith] >[5, Śmith] >[1, Zebra] >[3, Żebra] > at > org.apache.derbyTesting.junit.BaseTestCase.newAssertionFailedError(BaseTestCase.java:1177) > at org.apache.derbyTesting.junit.JDBC.addRsToReport(JDBC.java:1998) > at > org.apache.derbyTesting.junit.JDBC.assertRowInResultSet(JDBC.java:1497) > at > org.apache.derbyTesting.junit.JDBC.assertRowInResultSet(JDBC.java:1395) > at > org.apache.derbyTesting.junit.JDBC.assertFullResultSetMinion(JDBC.java:1257) > at > org.apache.derbyTesting.junit.JDBC.assertFullResultSet(JDBC.java:1168) > at > org.apache.derbyTesting.junit.JDBC.assertFullResultSet(JDBC.java:1125) > at > org.apache.derbyTesting.junit.JDBC.assertFullResultSet(JDBC.java:1083) > at > org.apache.derbyTesting.functionTests.tests.lang.CollationTest.checkLangBasedQuery(CollationTest.java:2055) > at > org.apache.derbyTesting.functionTests.tests.lang.CollationTest.testNorwayCollation(CollationTest.java:482) > at > org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:120) > at > org.apache.derbyTesting.junit.BaseJDBCTestCase.runBareOverridable(BaseJDBCTestCase.java:443) > at > org.apache.derbyTesting.junit.BaseJDBCTestCase.runBare(BaseJDBCTestCase.java:460) > 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 junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) >
[jira] [Commented] (DERBY-6876) Can't create triggers on a table - error 42X94
[ https://issues.apache.org/jira/browse/DERBY-6876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15217990#comment-15217990 ] Bryan Pendleton commented on DERBY-6876: Unfortunately, I don't know of a hard way, either; partly because I'm not certain I understand the precise damage that has occurred to sysdepends. Derby is open source, after all, so one way is to find and disable the part of Derby which prevents you from writing "normal" SQL against the system tables, and then figure out which rows in sysdepends are causing you the problem(s), and issue "delete from sysdepends where" statements to remove those rows. Or, if the issue is that sysdepends has the correct data, but the index conglomerate which provides access to sysdepends has become corrupted, then one way would be to cause Derby to drop the index on sysdepends, and re-create it. But I'm sorry to say I don't actually know how to accomplish those tasks; this is just me brainstorming off the top of my head. > Can't create triggers on a table - error 42X94 > -- > > Key: DERBY-6876 > URL: https://issues.apache.org/jira/browse/DERBY-6876 > Project: Derby > Issue Type: Bug > Environment: Linux x86_64, Java 1.8.0_74 >Reporter: Aleksei Kovura > Attachments: trigger_bug.zip > > > I previously shared this on dev mailing list - > http://thread.gmane.org/gmane.comp.apache.db.derby.devel/115427. > I'm reworking triggers in my database and getting this message while trying > to create one: > > Error: StoredPreparedStatement '19ba803c-014e-b216-6d98-0650b418' does > not exist. > SQLState: 42X94 > ErrorCode: 3 > > This database is a couple years old, started out as 10.10.1.1, was upgraded > to stable releases as they appeared (10.11.1.1 -> 10.12.1.1). Some DDL was > changed in between upgrades, unfortunately I can't track which ones and when. > SYSCS_UTIL.SYSCS_INVALIDATE_STORED_STATEMENTS() doesn't help. > I tried my best to create a replicable test case through creating database on > earlier versions, upgrading and playing with DDL - no such luck, so I'm > attaching compressed database (with data deleted and tables compressed). Bug > replication procedure is as follows: > 1) Unpack attached file (it has a "trigger_bug" root directory); > 2) Boot the db_trigger database in embedded mode, include "trigger_bug" > directory in the classpath - there is one Java class that is referenced in > Stored Procedure; > 3) Try to run this SQL: > CREATE TRIGGER APP."test" > AFTER UPDATE OF description ON APP."ACTIONS" > REFERENCING NEW ROW AS updated_row > FOR EACH ROW > UPDATE APP."ACTIONS" SET description = 'testing' > WHERE id=updated_row.id > 4) Get a 42X94 error. > I'm hoping someone with enough knowledge can poke around in system tables and > figure out what's going on. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DERBY-6876) Can't create triggers on a table - error 42X94
[ https://issues.apache.org/jira/browse/DERBY-6876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15217926#comment-15217926 ] Aleksei Kovura commented on DERBY-6876: --- Thanks Rick, I didn't think of that. I'm still trying to avoid messing with DDL, because it's under version control by flywaydb. [~bpendleton] Just to get some clarity on this: is there absolutely no hope of figuring out corruption issue and repairing this database? You wrote "I don't think there is any easy way to repair a damaged SYS.SYSDEPENDS table" - does that mean there's a hard way? :) > Can't create triggers on a table - error 42X94 > -- > > Key: DERBY-6876 > URL: https://issues.apache.org/jira/browse/DERBY-6876 > Project: Derby > Issue Type: Bug > Environment: Linux x86_64, Java 1.8.0_74 >Reporter: Aleksei Kovura > Attachments: trigger_bug.zip > > > I previously shared this on dev mailing list - > http://thread.gmane.org/gmane.comp.apache.db.derby.devel/115427. > I'm reworking triggers in my database and getting this message while trying > to create one: > > Error: StoredPreparedStatement '19ba803c-014e-b216-6d98-0650b418' does > not exist. > SQLState: 42X94 > ErrorCode: 3 > > This database is a couple years old, started out as 10.10.1.1, was upgraded > to stable releases as they appeared (10.11.1.1 -> 10.12.1.1). Some DDL was > changed in between upgrades, unfortunately I can't track which ones and when. > SYSCS_UTIL.SYSCS_INVALIDATE_STORED_STATEMENTS() doesn't help. > I tried my best to create a replicable test case through creating database on > earlier versions, upgrading and playing with DDL - no such luck, so I'm > attaching compressed database (with data deleted and tables compressed). Bug > replication procedure is as follows: > 1) Unpack attached file (it has a "trigger_bug" root directory); > 2) Boot the db_trigger database in embedded mode, include "trigger_bug" > directory in the classpath - there is one Java class that is referenced in > Stored Procedure; > 3) Try to run this SQL: > CREATE TRIGGER APP."test" > AFTER UPDATE OF description ON APP."ACTIONS" > REFERENCING NEW ROW AS updated_row > FOR EACH ROW > UPDATE APP."ACTIONS" SET description = 'testing' > WHERE id=updated_row.id > 4) Get a 42X94 error. > I'm hoping someone with enough knowledge can poke around in system tables and > figure out what's going on. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (DERBY-6881) Test failures with JDK 9-ea b111
Knut Anders Hatlen created DERBY-6881: - Summary: Test failures with JDK 9-ea b111 Key: DERBY-6881 URL: https://issues.apache.org/jira/browse/DERBY-6881 Project: Derby Issue Type: Bug Components: Test Affects Versions: 10.13.0.0 Reporter: Knut Anders Hatlen With JDK 9-ea b111 there are a number of test failures. Tests that use ClassLoaderTestSetup fail because the context class loader no longer is a URLClassLoader, which causes a ClassCastException in the class loader magic performed by the test setup: {noformat} java.lang.ClassCastException: jdk.internal.loader.ClassLoaders$AppClassLoader (in module: java.base) cannot be cast to java.net.URLClassLoader (in module: java.base) at org.apache.derbyTesting.junit.ClassLoaderTestSetup$1.run(ClassLoaderTestSetup.java:53) at org.apache.derbyTesting.junit.ClassLoaderTestSetup$1.run(ClassLoaderTestSetup.java:50) at java.security.AccessController.doPrivileged(java.base@9-ea/Native Method) at org.apache.derbyTesting.junit.ClassLoaderTestSetup.makeClassLoader(ClassLoaderTestSetup.java:49) at org.apache.derbyTesting.junit.ClassLoaderTestSetup.setUp(ClassLoaderTestSetup.java:64) at junit.extensions.TestSetup$1.protect(TestSetup.java:20) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:58) {noformat} CollationTest, CollationTest2, LocalizedAttributeScriptTest and LocalizedDisplayScriptTest have failures, for example: {noformat} junit.framework.AssertionFailedError: Column value mismatch @ column 'ID', row 1: Expected: >4< Found:>6< ID,NAME -- [6, aacorn] [4, Acorn] [2, Ącorn] [0, Smith] [5, Śmith] [1, Zebra] [3, Żebra] at org.apache.derbyTesting.junit.BaseTestCase.newAssertionFailedError(BaseTestCase.java:1177) at org.apache.derbyTesting.junit.JDBC.addRsToReport(JDBC.java:1998) at org.apache.derbyTesting.junit.JDBC.assertRowInResultSet(JDBC.java:1497) at org.apache.derbyTesting.junit.JDBC.assertRowInResultSet(JDBC.java:1395) at org.apache.derbyTesting.junit.JDBC.assertFullResultSetMinion(JDBC.java:1257) at org.apache.derbyTesting.junit.JDBC.assertFullResultSet(JDBC.java:1168) at org.apache.derbyTesting.junit.JDBC.assertFullResultSet(JDBC.java:1125) at org.apache.derbyTesting.junit.JDBC.assertFullResultSet(JDBC.java:1083) at org.apache.derbyTesting.functionTests.tests.lang.CollationTest.checkLangBasedQuery(CollationTest.java:2055) at org.apache.derbyTesting.functionTests.tests.lang.CollationTest.testNorwayCollation(CollationTest.java:482) at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:120) at org.apache.derbyTesting.junit.BaseJDBCTestCase.runBareOverridable(BaseJDBCTestCase.java:443) at org.apache.derbyTesting.junit.BaseJDBCTestCase.runBare(BaseJDBCTestCase.java:460) 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 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:58) 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) Caused by: junit.framework.AssertionFailedError: Column value mismatch @ column 'ID', row 1: Expected: >4< Found:>6< at org.apache.derbyTesting.junit.JDBC.assertRowInResultSet(JDBC.java:1492) {noformat} And the stack trace deletion patterns in the Sed class seem to be missing out on some stack frames now, causing failures like this one in dblook_test and dblook_test_territory: {noformat} * Diff file derbyall/derbytools/dblook_test.diff *** Start: dblook_test jdk9-ea derbyall:derbytools 2016-03-29 14:16:38 *** 6511a6512 > at java.io.FileInputStream.open0(java.base@9-ea/Native Method) Test Failed. {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332)