[ 
https://issues.apache.org/jira/browse/DERBY-4781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12900557#action_12900557
 ] 

Kathey Marsden commented on DERBY-4781:
---------------------------------------

I think that will resolve the failure with phoneme but weme is more serious.  
In weme we do not have the xml classes:

import org.w3c.dom.Document;
import org.w3c.dom.NodeList;


And this leads to an immediate and complete failure of suites.All with 
suite():java.lang.reflect.InvocationTargetException.

Running the test stand alone gives more information:
+ c:/cygwin/ibmsvn/ntsoftware/weme6.2/bin/j9 -jcl:foun11 -Demma.active= 
-Xbootclasspath
a:c:/cygwin/ibmsvn/ntsoftware/weme6.2/lib/jdbc.jar -Dbootcp=c:/cygwin/ibmsvn/nt
oftware/weme6.2/lib/jdbc.jar junit.textui.TestRunner org.apache.derbyTesting.fu
ctionTests.tests.lang.XplainStatisticsTest
Failed to invoke suite():java.lang.NoClassDefFoundError: org.w3c.dom.Document

I searched all the jars and zips in the weme distribution for this class and 
did not see it. Myrna is checking if there is an external jar somewhere 
available. If not we will need to do something in the test to load the classes 
dynamically if available and skip the fixture using them for weme. Hopefully 
that won't be necessary.




> suites.All fails completely with  Failed to invoke 
> suite():java.lang.reflect.InvocationTargetException  because of 
> XplainStatisticsTest
> ---------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-4781
>                 URL: https://issues.apache.org/jira/browse/DERBY-4781
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.7.0.0
>         Environment: java.fullversion: IBM J9 2.4 Windows XP x86-32  (JIT 
> enabled, AOT enabled)
> J9VM - 20080919_023055_lHdFGQ
> JIT  - r9.weme62_20080724_2131
> GC   - 20080609_AA
>            Reporter: Kathey Marsden
>            Assignee: C.S. Nirmal J. Fernando
>         Attachments: derby-4587-removeSplitMethod.diff
>
>
> weme 6.2 tests fail to kick off because of XplainStatisticsTest after the 
> change:
> r982637  DERBY-4587: Add tools for query plan analysis 
> The problem seems related to the import and use of 
> import org.w3c.dom.Document;
> import org.w3c.dom.NodeList;
> I am not sure if there are additional jars that I need to use to get these 
> libraries from the weme distribution or if they are available.   After this 
> same checkin the test also fails on CVM/phoneme with the error below but it 
> does not prevent the full suite from kicking off.
> ime: 15,558.801
> There was 1 error:
> 1) 
> testScanPositions(org.apache.derbyTesting.functionTests.tests.lang.XplainStatisticsTest)java.lang.NoSuchMethodError:
>  java.lang.String: method split(Ljava/lang/String;)[Ljava/lang/String; not 
> found
>       at 
> org.apache.derby.impl.tools.planexporter.AccessDatabase.replace(Unknown 
> Source)
>       at 
> org.apache.derby.impl.tools.planexporter.AccessDatabase.statement(Unknown 
> Source)
>       at 
> org.apache.derbyTesting.functionTests.tests.lang.XplainStatisticsTest.disableXplainStyle(Unknown
>  Source)
>       at 
> org.apache.derbyTesting.functionTests.tests.lang.XplainStatisticsTest.testScanPositions(Unknown
>  Source)
>       at org.apache.derbyTesting.junit.BaseTestCase.runBare(Unknown Source)
>       at junit.extensions.TestDecorator.basicRun(Unknown Source)
>       at junit.extensions.TestSetup$1.protect(Unknown Source)
>       at junit.extensions.TestSetup.run(Unknown Source)
>       at junit.extensions.TestDecorator.basicRun(Unknown Source)
>       at junit.extensions.TestSetup$1.protect(Unknown Source)
>       at junit.extensions.TestSetup.run(Unknown Source)
>       at org.apache.derbyTesting.junit.BaseTestSetup.run(Unknown Source)
>       at sun.misc.CVM.runMain(Unknown Source)
> FAILURES!!!
> http://dbtg.foundry.sun.com/derby/test/Daily/javaME/testing/testlog/ubuntu/983036-suitesAll_diff.txt

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to