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 "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2007/05/25 19:51:16 UTC
[jira] Reopened: (DERBY-2613) upgrade test problem when attempting
to test 10.0.2.1 -
[ https://issues.apache.org/jira/browse/DERBY-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren reopened DERBY-2613:
---------------------------------------
> upgrade test problem when attempting to test 10.0.2.1 -
> --------------------------------------------------------
>
> Key: DERBY-2613
> URL: https://issues.apache.org/jira/browse/DERBY-2613
> Project: Derby
> Issue Type: Bug
> Components: Regression Test Failure
> Affects Versions: 10.3.0.0
> Environment: m2_ibm15:435>sysinfo
> ------------------ Java Information ------------------
> Java Version: 1.5.0
> Java Vendor: IBM Corporation
> Java home: c:\p4\m2\ibm15\jre
> Java classpath: .;.;c:/p4/m2/classes;c:/p4/m2/tools/java/jdbctests.zip;c:/p4/m2
> /tools/java/jakarta-oro-2.0.8.jar;c:/p4/m2/tools/java/jgl3.1.0.jar;c:/p4/m2/tool
> s/java/jndi/providerutil.jar;c:/p4/m2/tools/java/jndi/ldap.jar;c:/p4/m2/tools/ja
> va/jndi/jndi.jar;c:/p4/m2/tools/java/jnl1.0F.zip;c:/p4/m2/tools/java/junit.jar;c
> :/p4/m2/tools/java/servlet-2_2b.jar;c:/p4/m2/tools/java/xslt4j-2_5_0/xercesImpl.
> jar;c:/p4/m2/tools/java/xslt4j-2_5_0/xml-apis.jar;c:/p4/m2/tools/java/xslt4j-2_5
> _0/xalan.jar
> OS name: Windows XP
> OS architecture: x86
> OS version: 5.1 build 2600 Service Pack 2
> Java user name: mikem
> Java user home: C:\Documents and Settings\Administrator
> Java user dir: C:\mikem\_tools
> java.specification.name: Java Platform API Specification
> java.specification.version: 1.5
> --------- Derby Information --------
> JRE - JDBC: J2SE 5.0 - JDBC 3.0
> [C:\p4\m2\classes] 10.3.0.0 alpha - (1)
> Reporter: Mike Matrigali
> Assigned To: Mike Matrigali
> Fix For: 10.3.0.0
>
>
> I am not sure what is broken here. it looks like a test problem, but that is only a guess. When I got this problem I was trying to run
> a full set of upgrade tests against the trunk and I had jars for all of the releases available from :
> https://svn.apache.org/repos/asf/db/derby/jars
> (ie. :
> m1_ibm15:64>ls */lib
> 10.0.2.1/lib:
> derby.jar derbyLocale_it.jar derbyLocale_zh_CN.jar
> derbyLocale_de_DE.jar derbyLocale_ja_JP.jar derbyLocale_zh_TW.jar
> derbyLocale_es.jar derbyLocale_ko_KR.jar derbynet.jar
> derbyLocale_fr.jar derbyLocale_pt_BR.jar derbytools.jar
> 10.1.1.0/lib:
> derby.jar derbyLocale_ja_JP.jar derbyTesting.jar
> derbyLocale_de_DE.jar derbyLocale_ko_KR.jar derbyclient.jar
> derbyLocale_es.jar derbyLocale_pt_BR.jar derbynet.jar
> derbyLocale_fr.jar derbyLocale_zh_CN.jar derbytools.jar
> derbyLocale_it.jar derbyLocale_zh_TW.jar
> 10.1.2.1/lib:
> derby.jar derbyLocale_ja_JP.jar derbyTesting.jar
> derbyLocale_de_DE.jar derbyLocale_ko_KR.jar derbyclient.jar
> derbyLocale_es.jar derbyLocale_pt_BR.jar derbynet.jar
> derbyLocale_fr.jar derbyLocale_zh_CN.jar derbytools.jar
> derbyLocale_it.jar derbyLocale_zh_TW.jar
> 10.1.3.1/lib:
> derby.jar derbyLocale_ja_JP.jar derbyTesting.jar
> derbyLocale_de_DE.jar derbyLocale_ko_KR.jar derbyclient.jar
> derbyLocale_es.jar derbyLocale_pt_BR.jar derbynet.jar
> derbyLocale_fr.jar derbyLocale_zh_CN.jar derbytools.jar
> derbyLocale_it.jar derbyLocale_zh_TW.jar
> 10.2.1.6/lib:
> derby.jar derbyLocale_ja_JP.jar derbyclient.jar
> derbyLocale_de_DE.jar derbyLocale_ko_KR.jar derbynet.jar
> derbyLocale_es.jar derbyLocale_pt_BR.jar derbyrun.jar
> derbyLocale_fr.jar derbyLocale_zh_CN.jar derbytools.jar
> derbyLocale_it.jar derbyLocale_zh_TW.jar
> 10.2.2.0/lib:
> derby.jar derbyLocale_ja_JP.jar derbyTesting.jar
> derbyLocale_cs.jar derbyLocale_ko_KR.jar derbyclient.jar
> derbyLocale_de_DE.jar derbyLocale_pl.jar derbynet.jar
> derbyLocale_es.jar derbyLocale_pt_BR.jar derbyrun.jar
> derbyLocale_fr.jar derbyLocale_ru.jar derbytools.jar
> derbyLocale_hu.jar derbyLocale_zh_CN.jar
> derbyLocale_it.jar derbyLocale_zh_TW.jar
> The phase that it broke in was when it was trying to test was the following hierarchy as reported by junit.swingui.TestRunner:
> Upgrade Suite
> Upgrade Tests from 10.0.2.1
> Upgrade Phase: UPGRADE
> It looks like this phase does not even get started as it can't find the db. Note in the same run there is one soft upgrade error that happens in a
> previous phase. I have reported that as a separate issue in DERBY-2612 .
> Here is the error reported:
> 2) Upgrade Phase: UPGRADEjava.sql.SQLException: Failed to start database 'single
> Use/oneuse0', see the next exception for details.
> at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(SQLExcepti
> onFactory.java:45)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Util.java:88)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Util.java:94)
> at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Util.java:173)
> at org.apache.derby.impl.jdbc.EmbedConnection.newSQLException(EmbedConnectio
> n.java:2119)
> at org.apache.derby.impl.jdbc.EmbedConnection.bootDatabase(EmbedConnection.j
> ava:1783)
> at org.apache.derby.impl.jdbc.EmbedConnection.<init>(EmbedConnection.java:24
> 9)
> at org.apache.derby.jdbc.Driver30.getNewEmbedConnection(Driver30.java:74)
> at org.apache.derby.jdbc.InternalDriver.connect(InternalDriver.java:209)
> at org.apache.derby.jdbc.EmbeddedDataSource.getConnection(EmbeddedDataSource
> .java:479)
> at org.apache.derby.jdbc.EmbeddedDataSource.getConnection(EmbeddedDataSource
> .java:423)
> at org.apache.derbyTesting.functionTests.tests.upgradeTests.PhaseChanger.set
> Up(PhaseChanger.java:94)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:18)
> at junit.extensions.TestSetup.run(TestSetup.java:23)
> at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> at junit.extensions.TestSetup.run(TestSetup.java:23)
> at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> at junit.extensions.TestSetup.run(TestSetup.java:23)
> at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> at junit.extensions.TestSetup.run(TestSetup.java:23)
> at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> at junit.extensions.TestSetup.run(TestSetup.java:23)
> at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> at junit.extensions.TestSetup.run(TestSetup.java:23)
> at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> at junit.extensions.TestSetup.run(TestSetup.java:23)
> at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> at junit.extensions.TestSetup.run(TestSetup.java:23)
> at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> at junit.extensions.TestSetup.run(TestSetup.java:23)
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.