[jira] [Commented] (DERBY-5977) Run storemore and possibly other store .sql tests in junit harness using ScriptTest mechanism.
[ https://issues.apache.org/jira/browse/DERBY-5977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13589693#comment-13589693 ] Myrna van Lunteren commented on DERBY-5977: --- I committed patch DERBY-5977_3.diff with revision 1451262 (http://svn.apache.org/viewvc?view=revision&revision=1451262). > Run storemore and possibly other store .sql tests in junit harness using > ScriptTest mechanism. > -- > > Key: DERBY-5977 > URL: https://issues.apache.org/jira/browse/DERBY-5977 > Project: Derby > Issue Type: Improvement > Components: Test >Reporter: Myrna van Lunteren >Assignee: Myrna van Lunteren > Attachments: DERBY-5977_1.diff, DERBY-5977_1.stat, DERBY-5977_2.diff, > DERBY-5977_2.stat, DERBY-5977_3.diff, DERBY-5977_3.diff, DERBY-5977_3.stat, > DERBY-5977_3.stat > > > There are a number of .sql tests in the storemore suite, which might be able > to in the junit framework through a scriptTest. > They can still be fully converted at a later stage if we need more control. > -- 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
[jira] [Commented] (DERBY-5977) Run storemore and possibly other store .sql tests in junit harness using ScriptTest mechanism.
[ https://issues.apache.org/jira/browse/DERBY-5977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13589286#comment-13589286 ] Myrna van Lunteren commented on DERBY-5977: --- forgot to mention; these changes pass derbyall and suites.All with ibm1.6 and weme6.2. > Run storemore and possibly other store .sql tests in junit harness using > ScriptTest mechanism. > -- > > Key: DERBY-5977 > URL: https://issues.apache.org/jira/browse/DERBY-5977 > Project: Derby > Issue Type: Improvement > Components: Test >Reporter: Myrna van Lunteren >Assignee: Myrna van Lunteren > Attachments: DERBY-5977_1.diff, DERBY-5977_1.stat, DERBY-5977_2.diff, > DERBY-5977_2.stat, DERBY-5977_3.diff, DERBY-5977_3.diff, DERBY-5977_3.stat, > DERBY-5977_3.stat > > > There are a number of .sql tests in the storemore suite, which might be able > to in the junit framework through a scriptTest. > They can still be fully converted at a later stage if we need more control. > -- 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
[jira] [Commented] (DERBY-5977) Run storemore and possibly other store .sql tests in junit harness using ScriptTest mechanism.
[ https://issues.apache.org/jira/browse/DERBY-5977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13581844#comment-13581844 ] Myrna van Lunteren commented on DERBY-5977: --- I tried to make a StoreHarnessJavaTest, similar to LangHarnessJavaTest, with the .java tests from the storemore suite. However, only 1 test of this passed (OnlineCompressTest), so I don't think it's worth while adding such a wrapper, I think it's better to do the actual conversion to junit for these. > Run storemore and possibly other store .sql tests in junit harness using > ScriptTest mechanism. > -- > > Key: DERBY-5977 > URL: https://issues.apache.org/jira/browse/DERBY-5977 > Project: Derby > Issue Type: Improvement > Components: Test >Reporter: Myrna van Lunteren >Assignee: Myrna van Lunteren > Attachments: DERBY-5977_1.diff, DERBY-5977_1.stat, DERBY-5977_2.diff, > DERBY-5977_2.stat, DERBY-5977_3.diff, DERBY-5977_3.stat > > > There are a number of .sql tests in the storemore suite, which might be able > to in the junit framework through a scriptTest. > They can still be fully converted at a later stage if we need more control. > -- 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
[jira] [Commented] (DERBY-5977) Run storemore and possibly other store .sql tests in junit harness using ScriptTest mechanism.
[ https://issues.apache.org/jira/browse/DERBY-5977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13578421#comment-13578421 ] Myrna van Lunteren commented on DERBY-5977: --- committed patch 3 with revision 1446227 (http://svn.apache.org/viewvc?view=revision&revision=1446227) > Run storemore and possibly other store .sql tests in junit harness using > ScriptTest mechanism. > -- > > Key: DERBY-5977 > URL: https://issues.apache.org/jira/browse/DERBY-5977 > Project: Derby > Issue Type: Improvement > Components: Test >Reporter: Myrna van Lunteren >Assignee: Myrna van Lunteren > Attachments: DERBY-5977_1.diff, DERBY-5977_1.stat, DERBY-5977_2.diff, > DERBY-5977_2.stat, DERBY-5977_3.diff, DERBY-5977_3.stat > > > There are a number of .sql tests in the storemore suite, which might be able > to in the junit framework through a scriptTest. > They can still be fully converted at a later stage if we need more control. > -- 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
[jira] [Commented] (DERBY-5977) Run storemore and possibly other store .sql tests in junit harness using ScriptTest mechanism.
[ https://issues.apache.org/jira/browse/DERBY-5977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13578100#comment-13578100 ] Myrna van Lunteren commented on DERBY-5977: --- For completeness' sake, the AccessTest fixture that failed before, was testLoadLongColumnsCreateIndex (and in some cases, after attempted rollback, a subsequent fixture expected the same error, but did not get it). Here's a snippet from a stack trace: java.sql.SQLException: Limitation: Record of a btree secondary index cannot be updated or inserted due to lack of space on the page. Use the parameters derby.storage.pageSize and/or derby.storage.pageReservedSpace to work around this limitation. at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(SQLExceptionFactory40.java:98) at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Util.java:256) at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(TransactionResourceImpl.java:424) at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(TransactionResourceImpl.java:353) at org.apache.derby.impl.jdbc.EmbedConnection.handleException(EmbedConnection.java:2400) at org.apache.derby.impl.jdbc.ConnectionChild.handleException(ConnectionChild.java:82) at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(EmbedStatement.java:1334) at org.apache.derby.impl.jdbc.EmbedStatement.execute(EmbedStatement.java:630) at org.apache.derby.impl.jdbc.EmbedStatement.executeUpdate(EmbedStatement.java:179) at org.apache.derbyTesting.functionTests.tests.store.AccessTest.testLoadLongColumnsCreateIndex(AccessTest.java:822) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:611) at junit.framework.TestCase.runTest(TestCase.java:164) at junit.framework.TestCase.runBare(TestCase.java:130) 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.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:120) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.framework.TestResult.runProtected(TestResult.java:124) 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.framework.TestResult.runProtected(TestResult.java:124) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.extensions.TestSetup.run(TestSetup.java:25) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at junit.textui.TestRunner.doRun(TestRunner.java:121) at junit.textui.TestRunner.start(TestRunner.java:185) at junit.textui.TestRunner.main(TestRunner.java:143) Caused by: java.sql.SQLException: Limitation: Record of a btree secondary index cannot be updated or inserted due to lack of space on the page. Use the parameters derby.storage.pageSize and/or derby.storage.pageReservedSpace to work around this limitation. at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(SQLExceptionFactory.java:42) at org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(SQLExceptionFactory40.java:122) at org
[jira] [Commented] (DERBY-5977) Run storemore and possibly other store .sql tests in junit harness using ScriptTest mechanism.
[ https://issues.apache.org/jira/browse/DERBY-5977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13574118#comment-13574118 ] Myrna van Lunteren commented on DERBY-5977: --- I committed patch DERBY-5977_2 to trunk with revision 1443812 (http://svn.apache.org/viewvc?view=revision&revision=1443812). I'll next look at enabling databaseProperties.sql in the new StoreScriptsTest. > Run storemore and possibly other store .sql tests in junit harness using > ScriptTest mechanism. > -- > > Key: DERBY-5977 > URL: https://issues.apache.org/jira/browse/DERBY-5977 > Project: Derby > Issue Type: Improvement > Components: Test >Reporter: Myrna van Lunteren >Assignee: Myrna van Lunteren > Attachments: DERBY-5977_1.diff, DERBY-5977_1.stat, DERBY-5977_2.diff, > DERBY-5977_2.stat > > > There are a number of .sql tests in the storemore suite, which might be able > to in the junit framework through a scriptTest. > They can still be fully converted at a later stage if we need more control. > -- 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
[jira] [Commented] (DERBY-5977) Run storemore and possibly other store .sql tests in junit harness using ScriptTest mechanism.
[ https://issues.apache.org/jira/browse/DERBY-5977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13574087#comment-13574087 ] Mike Matrigali commented on DERBY-5977: --- can you ever tell what test/line the error is coming on. It would be good to understand if the test is expecting a btree with a large page size so that it can do inserts, but for some reason either system property or database property the index has a smaller page size. That is the usual case and not a bug in the code. > Run storemore and possibly other store .sql tests in junit harness using > ScriptTest mechanism. > -- > > Key: DERBY-5977 > URL: https://issues.apache.org/jira/browse/DERBY-5977 > Project: Derby > Issue Type: Improvement > Components: Test >Reporter: Myrna van Lunteren >Assignee: Myrna van Lunteren > Attachments: DERBY-5977_1.diff, DERBY-5977_1.stat, DERBY-5977_2.diff, > DERBY-5977_2.stat > > > There are a number of .sql tests in the storemore suite, which might be able > to in the junit framework through a scriptTest. > They can still be fully converted at a later stage if we need more control. > -- 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
[jira] [Commented] (DERBY-5977) Run storemore and possibly other store .sql tests in junit harness using ScriptTest mechanism.
[
https://issues.apache.org/jira/browse/DERBY-5977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13574081#comment-13574081
]
Mike Matrigali commented on DERBY-5977:
---
at one point in the databaseProperties test it sets that SYSTEM pageSize. This
is likely causing at least some of the problems. Best would be to change the
test to unset the system property after it does the test it is trying to do. I
don't see an existing utility, so may need to add one.
Do you know in the new environment if the test is run with autocommit on or
off? I would suggest running the test with autocommit off and then run an
abort at the end
of the script.
Here is a web hit on how to delete
a system property:
8/30/2006
How to Remove a System Property
I thought I could remove a system property by setting its value to null, but it
turns out that System.setProperty(key, val) will throw NullPointerException
when either key or value is null. Here are 2 ways to remove or clear a system
property:
1. clearProperty(String key) introduced in JDK 1.5.
System.clearProperty("key");
2.
Properties sysProps = System.getProperties();
sysProps.remove("key");
When java security manager is enabled, Both methods need specific permissions
to succeed. Approach 1 requires PropertyPermission "key", "read,write".
Approach 2 requires a much wider permission: PropertyPermission "*",
"read,write", because you are free to modify/remove all system properties with
the returned object from System.getProperties()
> Run storemore and possibly other store .sql tests in junit harness using
> ScriptTest mechanism.
> --
>
> Key: DERBY-5977
> URL: https://issues.apache.org/jira/browse/DERBY-5977
> Project: Derby
> Issue Type: Improvement
> Components: Test
>Reporter: Myrna van Lunteren
>Assignee: Myrna van Lunteren
> Attachments: DERBY-5977_1.diff, DERBY-5977_1.stat, DERBY-5977_2.diff,
> DERBY-5977_2.stat
>
>
> There are a number of .sql tests in the storemore suite, which might be able
> to in the junit framework through a scriptTest.
> They can still be fully converted at a later stage if we need more control.
>
--
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
[jira] [Commented] (DERBY-5977) Run storemore and possibly other store .sql tests in junit harness using ScriptTest mechanism.
[ https://issues.apache.org/jira/browse/DERBY-5977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13530693#comment-13530693 ] Mamta A. Satoor commented on DERBY-5977: Hi Myrna, thanks for working on this issue. I looked at the part of the patch where you are setting "ij.protocol" to "jdbc:derby:". But for J2ME platforms, you probably need to set "ij.dataSource" property. I think including the relevant ij properties for J2ME should take care of connect "wombat" without having to change them to connect 'jdbc:derby;wombat'. > Run storemore and possibly other store .sql tests in junit harness using > ScriptTest mechanism. > -- > > Key: DERBY-5977 > URL: https://issues.apache.org/jira/browse/DERBY-5977 > Project: Derby > Issue Type: Improvement > Components: Test >Reporter: Myrna van Lunteren >Assignee: Myrna van Lunteren > Attachments: DERBY-5977_1.diff, DERBY-5977_1.stat > > > There are a number of .sql tests in the storemore suite, which might be able > to in the junit framework through a scriptTest. > They can still be fully converted at a later stage if we need more control. > -- 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
