You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Vladimir Beliaev (JIRA)" <ji...@apache.org> on 2007/12/19 11:45:43 UTC
[jira] Commented: (HARMONY-3850) [classlib][EUT] 2 EUT tests from
core.runtime suite fail
[ https://issues.apache.org/jira/browse/HARMONY-3850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553295 ]
Vladimir Beliaev commented on HARMONY-3850:
-------------------------------------------
The issues is still reproducible on M4 release:
testRootElementAndDTDDescriber failes with:
5.1 expected:<org.eclipse.core.tests.runtime.root-element> but was:<org.eclipse.core.runtime.xml>
junit.framework.AssertionFailedError: 5.1 expected:<org.eclipse.core.tests.runtime.root-element> but was:<org.eclipse.core.runtime.xml>
at org.eclipse.core.tests.runtime.content.IContentTypeManagerTest.testRootElementAndDTDDescriber(IContentTypeManagerTest.java:1203)
at java.lang.reflect.VMReflection.invokeMethod(VMReflection.java)
at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:354)
at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:206)
at org.eclipse.test.CoreTestApplication.runTests(CoreTestApplication.java:35)
at org.eclipse.test.CoreTestApplication.run(CoreTestApplication.java:31)
at java.lang.reflect.VMReflection.invokeMethod(VMReflection.java)
at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethod(EclipseAppContainer.java:533)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:155)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
at java.lang.reflect.VMReflection.invokeMethod(VMReflection.java)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:504)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:443)
at org.eclipse.equinox.launcher.Main.run(Main.java:1169)
at org.eclipse.equinox.launcher.Main.main(Main.java:1144)
at org.eclipse.core.launcher.Main.main(Main.java:30)
So it is the same symptom as it was.
I recommend:
1. doing this JIRA as a separate bug, not a sub-task
2. change its summary to: [classlib][eut] testRootElementAndDTDDescriber fails due to encoding issues
3. close H3343 as FIXED (because it was a complex JIRA and set of its issues were fixed)
Thanks
Vladimir Beliaev
> [classlib][EUT] 2 EUT tests from core.runtime suite fail
> --------------------------------------------------------
>
> Key: HARMONY-3850
> URL: https://issues.apache.org/jira/browse/HARMONY-3850
> Project: Harmony
> Issue Type: Sub-task
> Components: Classlib
> Reporter: George Timoshenko
>
> tests
> testContentDescription
> testRootElementAndDTDDescriber
> fail on DRLVM in OPT JET and interpreter modes.
> And they also fail on J9+Harmony classlib.
> See parent issue for the output example.
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.