You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Deepa Remesh (JIRA)" <de...@db.apache.org> on 2006/03/04 00:31:39 UTC
[jira] Created: (DERBY-1076) Resolve the ouput differences in
upgrade test
Resolve the ouput differences in upgrade test
---------------------------------------------
Key: DERBY-1076
URL: http://issues.apache.org/jira/browse/DERBY-1076
Project: Derby
Type: Sub-task
Components: Test
Reporter: Deepa Remesh
Priority: Minor
Fix For: 10.2.0.0
The output of running the upgrade test script (runphases.ksh) differs from what is checked into the master file (java\testing\org\apache\derbyTesting\functionTests\master\phaseTester.out). These differences need to be checked to see there are no real issues in the upgrade itself.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-1076) Resolve the ouput differences in
upgrade test
Posted by "Deepa Remesh (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1076?page=all ]
Deepa Remesh updated DERBY-1076:
--------------------------------
Attachment: derby-1076_metadata_test.diff
Attaching a patch 'derby-1076_metadata_test.diff' which is a one-line change in metadata_test.java. The change is to cleanup the test objects at beginning of test to allow the upgrade test to continue if there are intermittent failures. This patch reduces the diffs (Table/View 'T' already exists in Schema 'APP'. ) mentioned in the previous comment and helps to continue with my work on DERBY-1075.
This patch changes only tests. With this patch, I ran the metadata tests (jdbcapi/metadata.java and odbc_metadata.java) in all three frameworks with Sun jdk1.4.2. Please take a look at this patch.
> Resolve the ouput differences in upgrade test
> ---------------------------------------------
>
> Key: DERBY-1076
> URL: http://issues.apache.org/jira/browse/DERBY-1076
> Project: Derby
> Type: Sub-task
> Components: Test
> Reporter: Deepa Remesh
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: derby-1076_metadata_test.diff, phaseTester.diff, phaseTester.out
>
> The output of running the upgrade test script (runphases.ksh) differs from what is checked into the master file (java\testing\org\apache\derbyTesting\functionTests\master\phaseTester.out). These differences need to be checked to see there are no real issues in the upgrade itself.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
Re: [jira] Updated: (DERBY-1076) Resolve the ouput differences in upgrade test
Posted by Deepa Remesh <dr...@gmail.com>.
On 3/10/06, Satheesh Bandaram <sa...@sourcery.org> wrote:
> The first failure seems to mean either SYS.SYSCOLPERMS is not getting
> created as part of hard upgrade or more likely, 10.2 metadata query is
> referencing SYS.SYSCOLPERMS which is not be present in soft upgrade mode. If
> you can confirm which one of these is the problem, I can look into this.
The first failure is in soft upgrade mode. Thanks Satheesh for looking
into this.
Deepa
[jira] Updated: (DERBY-1076) Resolve the ouput differences in
upgrade test
Posted by "Deepa Remesh (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1076?page=all ]
Deepa Remesh updated DERBY-1076:
--------------------------------
Attachment: phaseTester.diff
phaseTester.out
When I run the upgrade test on my machine, I get a huge diff. I am attaching the diff and out file. There are few diffs caused by difference in version (10.1.2.2 vs 10.1.2.3) and machine-specific locations. Other than that, the main diffs are caused by the following exceptions in the output:
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
getColumnPrivileges():
FAIL -- unexpected exception
SQLSTATE(42X05):ERROR 42X05: Table 'SYS.SYSCOLPERMS' does not exist.
at org.apache.derby.iapi.error.StandardException.newException(StandardException.java:311)
at org.apache.derby.impl.sql.compile.FromBaseTable.bindTableDescriptor(FromBaseTable.java:2382)
at org.apache.derby.impl.sql.compile.FromBaseTable.bindNonVTITables(FromBaseTable.java:2120)
at org.apache.derby.impl.sql.compile.FromList.bindTables(FromList.java:303)
at org.apache.derby.impl.sql.compile.SelectNode.bindNonVTITables(SelectNode.java:471)
at org.apache.derby.impl.sql.compile.DMLStatementNode.bindTables(DMLStatementNode.java:220)
at org.apache.derby.impl.sql.compile.DMLStatementNode.bind(DMLStatementNode.java:158)
at org.apache.derby.impl.sql.compile.CursorNode.bind(CursorNode.java:252)
at org.apache.derby.impl.sql.GenericStatement.prepMinion(GenericStatement.java:344)
at org.apache.derby.impl.sql.GenericStatement.prepare(GenericStatement.java:118)
at org.apache.derby.impl.sql.conn.GenericLanguageConnectionContext.prepareInternalStatement(GenericLanguageConnectionContext.java:721)
at org.apache.derby.impl.jdbc.EmbedPreparedStatement.<init>(EmbedPreparedStatement.java:118)
at org.apache.derby.impl.jdbc.EmbedPreparedStatement20.<init>(EmbedPreparedStatement20.java:82)
at org.apache.derby.impl.jdbc.EmbedPreparedStatement30.<init>(EmbedPreparedStatement30.java:62)
at org.apache.derby.jdbc.Driver30.newEmbedPreparedStatement(Driver30.java:92)
at org.apache.derby.impl.jdbc.EmbedConnection.prepareMetaDataStatement(EmbedConnection.java:1614)
at org.apache.derby.impl.jdbc.EmbedDatabaseMetaData.getPreparedQuery(EmbedDatabaseMetaData.java:3172)
at org.apache.derby.impl.jdbc.EmbedDatabaseMetaData.getColumnPrivileges(EmbedDatabaseMetaData.java:1798)
at org.apache.derbyTesting.functionTests.tests.jdbcapi.metadata.getMetaDataRS(metadata.java:113)
at org.apache.derbyTesting.functionTests.tests.jdbcapi.metadata_test.runTest(metadata_test.java:729)
at org.apache.derbyTesting.upgradeTests.phaseTester.main(phaseTester.java:177)
Test metadata finished
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Test metadata starting
FAIL -- unexpected exception
SQLSTATE(X0Y32):ERROR X0Y32: Table/View 'T' already exists in Schema 'APP'.
at org.apache.derby.iapi.error.StandardException.newException(StandardException.java:344)
at org.apache.derby.impl.sql.catalog.DataDictionaryImpl.duplicateDescriptorException(DataDictionaryImpl.java:1505)
at org.apache.derby.impl.sql.catalog.DataDictionaryImpl.addDescriptorNow(DataDictionaryImpl.java:1496)
at org.apache.derby.impl.sql.catalog.DataDictionaryImpl.addDescriptor(DataDictionaryImpl.java:1478)
at org.apache.derby.impl.sql.execute.CreateTableConstantAction.executeConstantAction(CreateTableConstantAction.java:223)
at org.apache.derby.impl.sql.execute.MiscResultSet.open(MiscResultSet.java:56)
at org.apache.derby.impl.sql.GenericPreparedStatement.execute(GenericPreparedStatement.java:379)
at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(EmbedStatement.java:1108)
at org.apache.derby.impl.jdbc.EmbedStatement.execute(EmbedStatement.java:517)
at org.apache.derby.impl.jdbc.EmbedStatement.execute(EmbedStatement.java:475)
at org.apache.derbyTesting.functionTests.tests.jdbcapi.metadata_test.runTest(metadata_test.java:190)
at org.apache.derbyTesting.upgradeTests.phaseTester.main(phaseTester.java:177)
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
FAIL -- unexpected exception
SQLSTATE(X0Y32):ERROR X0Y32: Table/View 'T' already exists in Schema 'APP'.
at org.apache.derby.iapi.error.StandardException.newException(StandardException.java:392)
at org.apache.derby.impl.sql.catalog.DataDictionaryImpl.duplicateDescriptorException(DataDictionaryImpl.java:1606)
at org.apache.derby.impl.sql.catalog.DataDictionaryImpl.addDescriptorNow(DataDictionaryImpl.java:1597)
at org.apache.derby.impl.sql.catalog.DataDictionaryImpl.addDescriptor(DataDictionaryImpl.java:1579)
at org.apache.derby.impl.sql.execute.CreateTableConstantAction.executeConstantAction(CreateTableConstantAction.java:223)
at org.apache.derby.impl.sql.execute.MiscResultSet.open(MiscResultSet.java:56)
at org.apache.derby.impl.sql.GenericPreparedStatement.execute(GenericPreparedStatement.java:361)
at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(EmbedStatement.java:1142)
at org.apache.derby.impl.jdbc.EmbedStatement.execute(EmbedStatement.java:550)
at org.apache.derby.impl.jdbc.EmbedStatement.execute(EmbedStatement.java:480)
at org.apache.derbyTesting.functionTests.tests.jdbcapi.metadata_test.runTest(metadata_test.java:190)
at org.apache.derbyTesting.upgradeTests.phaseTester.main(phaseTester.java:177)
Test metadata finished
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I would appreciate if someone else can also take a look and help me figure out the cause for these differences.
Note: For details of running the upgrade test, please see Mamta's comment at http://issues.apache.org/jira/browse/DERBY-573#action_12359550
> Resolve the ouput differences in upgrade test
> ---------------------------------------------
>
> Key: DERBY-1076
> URL: http://issues.apache.org/jira/browse/DERBY-1076
> Project: Derby
> Type: Sub-task
> Components: Test
> Reporter: Deepa Remesh
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: phaseTester.diff, phaseTester.out
>
> The output of running the upgrade test script (runphases.ksh) differs from what is checked into the master file (java\testing\org\apache\derbyTesting\functionTests\master\phaseTester.out). These differences need to be checked to see there are no real issues in the upgrade itself.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1076) Resolve the ouput differences in
upgrade test
Posted by "Knut Anders Hatlen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1076?page=comments#action_12372722 ]
Knut Anders Hatlen commented on DERBY-1076:
-------------------------------------------
The patch looks good, but the recent DERBY-690 check-in added some lines to the output from the metadata test. I can commit the patch if you update it with the new output.
> Resolve the ouput differences in upgrade test
> ---------------------------------------------
>
> Key: DERBY-1076
> URL: http://issues.apache.org/jira/browse/DERBY-1076
> Project: Derby
> Type: Sub-task
> Components: Test, Regression Test Failure
> Reporter: Deepa Remesh
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: derby-1076_master_update.diff, derby-1076_metadata_test.diff, phaseTester.diff, phaseTester.out
>
> The output of running the upgrade test script (runphases.ksh) differs from what is checked into the master file (java\testing\org\apache\derbyTesting\functionTests\master\phaseTester.out). These differences need to be checked to see there are no real issues in the upgrade itself.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (DERBY-1076) Resolve the ouput differences in
upgrade test
Posted by "Deepa Remesh (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1076?page=all ]
Deepa Remesh closed DERBY-1076:
-------------------------------
> Resolve the ouput differences in upgrade test
> ---------------------------------------------
>
> Key: DERBY-1076
> URL: http://issues.apache.org/jira/browse/DERBY-1076
> Project: Derby
> Type: Sub-task
> Components: Test, Regression Test Failure
> Reporter: Deepa Remesh
> Assignee: Deepa Remesh
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: derby-1076_master_update.diff, derby-1076_master_update_v2.diff, derby-1076_metadata_test.diff, phaseTester.diff, phaseTester.out
>
> The output of running the upgrade test script (runphases.ksh) differs from what is checked into the master file (java\testing\org\apache\derbyTesting\functionTests\master\phaseTester.out). These differences need to be checked to see there are no real issues in the upgrade itself.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (DERBY-1076) Resolve the ouput differences in
upgrade test
Posted by "Knut Anders Hatlen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1076?page=all ]
Knut Anders Hatlen resolved DERBY-1076:
---------------------------------------
Resolution: Fixed
Assign To: Deepa Remesh
Thanks Deepa, the upgrade test now runs cleanly (except from the identifiers). Committed revision 391255.
> Resolve the ouput differences in upgrade test
> ---------------------------------------------
>
> Key: DERBY-1076
> URL: http://issues.apache.org/jira/browse/DERBY-1076
> Project: Derby
> Type: Sub-task
> Components: Test, Regression Test Failure
> Reporter: Deepa Remesh
> Assignee: Deepa Remesh
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: derby-1076_master_update.diff, derby-1076_master_update_v2.diff, derby-1076_metadata_test.diff, phaseTester.diff, phaseTester.out
>
> The output of running the upgrade test script (runphases.ksh) differs from what is checked into the master file (java\testing\org\apache\derbyTesting\functionTests\master\phaseTester.out). These differences need to be checked to see there are no real issues in the upgrade itself.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-1076) Resolve the ouput differences in
upgrade test
Posted by "Deepa Remesh (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1076?page=all ]
Deepa Remesh updated DERBY-1076:
--------------------------------
Attachment: derby-1076_master_update.diff
Attaching a patch 'derby-1076_master_update.diff' which updates the master file for upgrade test. The master file is updated to reflect changes in the metadata test. Also there were extra lines in the master file in the previous checkin. I have also replaced 10.1.2.2 with 10.1.2.1 as Knut had suggested. This version info will hopefully go away with my next patch to allow running the test as part of harness. Still there are few diffs because of the diffs in the generated SQL id which look like this line:
,APP,REFACTION1,A,,APP,REFACTNONE,A,1,3,3,SQL060329093642910,SQL060329093642450,7
This will also go away once the test can be run with the harness, which filters out the generated ids.
This patch modifies only a master file. Please take a look at this patch. Thanks.
> Resolve the ouput differences in upgrade test
> ---------------------------------------------
>
> Key: DERBY-1076
> URL: http://issues.apache.org/jira/browse/DERBY-1076
> Project: Derby
> Type: Sub-task
> Components: Test, Regression Test Failure
> Reporter: Deepa Remesh
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: derby-1076_master_update.diff, derby-1076_metadata_test.diff, phaseTester.diff, phaseTester.out
>
> The output of running the upgrade test script (runphases.ksh) differs from what is checked into the master file (java\testing\org\apache\derbyTesting\functionTests\master\phaseTester.out). These differences need to be checked to see there are no real issues in the upgrade itself.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-1076) Resolve the ouput differences in
upgrade test
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1076?page=all ]
Kathey Marsden updated DERBY-1076:
----------------------------------
Component: Regression Test Failure
It seems to me that perhaps this issue should be Blocker and not Minor as marked.
If the upgrade tests are broken, how can we release 10.2? Rick do you have an opinion as release manager?
Deepa could you summarize any analysis you have done on the diffs?
> Resolve the ouput differences in upgrade test
> ---------------------------------------------
>
> Key: DERBY-1076
> URL: http://issues.apache.org/jira/browse/DERBY-1076
> Project: Derby
> Type: Sub-task
> Components: Test, Regression Test Failure
> Reporter: Deepa Remesh
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: derby-1076_metadata_test.diff, phaseTester.diff, phaseTester.out
>
> The output of running the upgrade test script (runphases.ksh) differs from what is checked into the master file (java\testing\org\apache\derbyTesting\functionTests\master\phaseTester.out). These differences need to be checked to see there are no real issues in the upgrade itself.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-1076) Resolve the ouput differences in
upgrade test
Posted by "Deepa Remesh (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1076?page=all ]
Deepa Remesh updated DERBY-1076:
--------------------------------
Attachment: derby-1076_master_update_v2.diff
Thanks Knut for looking at the patch. I am attaching a second version of patch 'derby-1076_master_update_v2.diff' with the added lines from the metadata test.
> Resolve the ouput differences in upgrade test
> ---------------------------------------------
>
> Key: DERBY-1076
> URL: http://issues.apache.org/jira/browse/DERBY-1076
> Project: Derby
> Type: Sub-task
> Components: Test, Regression Test Failure
> Reporter: Deepa Remesh
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: derby-1076_master_update.diff, derby-1076_master_update_v2.diff, derby-1076_metadata_test.diff, phaseTester.diff, phaseTester.out
>
> The output of running the upgrade test script (runphases.ksh) differs from what is checked into the master file (java\testing\org\apache\derbyTesting\functionTests\master\phaseTester.out). These differences need to be checked to see there are no real issues in the upgrade itself.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1076) Resolve the ouput differences in
upgrade test
Posted by "Deepa Remesh (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1076?page=comments#action_12370779 ]
Deepa Remesh commented on DERBY-1076:
-------------------------------------
Kathey, I agree that we should be able to run upgrade tests to check that upgrade does not have problems before 10.2 is released.
I am continuing the effort put into upgrade test by Mamta, Dan and others and trying to make it run as part of derbyall. Currently, I think it is difficult to test the upgrade mainly because of two things:
* Test is not part of derbyall. We have to run the test and compare the master files manually.
* Running manually is also a problem because of the existing diffs in the master file
>From what I have seen, the diffs are caused by following:
* Failure in DatabaseMetadata.getColumnPrivileges (DERBY-1121). Because of this, metadata test does not run to completion after soft upgrade. Maybe, as a test, we should modify the metadata test to ignore this exception and run the test after soft upgrade. This is just to make sure there are no other problems further along the test. I'll try this.
* Master updates in metadata test not reflected in phaseTester.out. The major part of phaseTester.out is the output of metadata test. After each phase, metadata test is run. phaseTester.out has to be updated to reflect the changes which have happened in the meantime.
* The master file is created with version 10.1.2.2. If we run the test with another version say, 10.1.2.4, there will be diffs. It will be good to avoid version information in the master file and do the necessary checking inside the test itself. I am working on this in DERBY-1075.
* Some machine specific locations in the file. We can avoid printing this to the output. I am doing this is DERBY-1075.
Proposal:
I have a draft patch attached to DERBY-1075 and would appreciate feedback on it. This patch creates a java class which can be used to write upgrade tests. Once this patch is reviewed and okay, we can then proceed to create upgrade tests. This should allow anybody to run the tests using the test harness. Once the output differences are resolved, we can add the tests to a suite and make it part of derbyall run. Does this sound reasonable?
> Resolve the ouput differences in upgrade test
> ---------------------------------------------
>
> Key: DERBY-1076
> URL: http://issues.apache.org/jira/browse/DERBY-1076
> Project: Derby
> Type: Sub-task
> Components: Test, Regression Test Failure
> Reporter: Deepa Remesh
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: derby-1076_metadata_test.diff, phaseTester.diff, phaseTester.out
>
> The output of running the upgrade test script (runphases.ksh) differs from what is checked into the master file (java\testing\org\apache\derbyTesting\functionTests\master\phaseTester.out). These differences need to be checked to see there are no real issues in the upgrade itself.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-1076) Resolve the ouput differences in
upgrade test
Posted by "Deepa Remesh (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1076?page=all ]
Deepa Remesh updated DERBY-1076:
--------------------------------
Derby Info: [Patch Available]
> Resolve the ouput differences in upgrade test
> ---------------------------------------------
>
> Key: DERBY-1076
> URL: http://issues.apache.org/jira/browse/DERBY-1076
> Project: Derby
> Type: Sub-task
> Components: Test, Regression Test Failure
> Reporter: Deepa Remesh
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: derby-1076_master_update.diff, derby-1076_master_update_v2.diff, derby-1076_metadata_test.diff, phaseTester.diff, phaseTester.out
>
> The output of running the upgrade test script (runphases.ksh) differs from what is checked into the master file (java\testing\org\apache\derbyTesting\functionTests\master\phaseTester.out). These differences need to be checked to see there are no real issues in the upgrade itself.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira