harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vasily Zakharov (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-3390) [JDK][EUT] 1 test fails from org.eclipse.jdt.apt.tests suit
Date Wed, 23 May 2007 13:48:16 GMT

    [ https://issues.apache.org/jira/browse/HARMONY-3390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498237
] 

Vasily Zakharov commented on HARMONY-3390:
------------------------------------------

Aleksey,

I've tried to reproduce the problem the way you described, and "ant -Dtests=jdtapt" produces
"Unexpected failures (88)", none of which looks like the problem described in this issue.
I used the latest EUT scripts from HARMONY-3556.

Are there any additional configurations to be made for the problem to be reproduced, any hardware
requirements or something?

Is there a way to run the testMirror test separately of the other jdtapt tests, to save reproduction
time?

Thank you!


> [JDK][EUT] 1 test fails from org.eclipse.jdt.apt.tests suit
> -----------------------------------------------------------
>
>                 Key: HARMONY-3390
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3390
>             Project: Harmony
>          Issue Type: Bug
>          Components: JDK
>            Reporter: Aleksey Ignatenko
>
> 1 test fails from org.eclipse.jdt.apt.tests suit.
> Stack trace:
> classname="org.eclipse.jdt.apt.tests.MirrorTests" name="testMirror"
>       <failure message=" ----------- Expected ------------ NO ERRORS ------------
but was ------------ java.lang.IllegalStateException: Failed during test:  Ex
> pected 79, but saw 74. Reason: Number of classes in java.util --------- Difference is
----------  expected:&lt;NO ERRORS&gt; but  was:&lt;java.lang.IllegalStat
> eException: Failed during test: Expected 79, but saw 74. Reason: Number of classes in
java.util&gt;"  type="junit.framework.ComparisonFailure">junit.framework.
> ComparisonFailure:
> The test is to be checked that it is definitly HY bug, possible that it is Eclipse bug.

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


Mime
View raw message