harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ilya Berezhniuk (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-4631) [drlvm][EUT] 126 jdtdebug tests failed w/ due to suspension issue
Date Tue, 18 Sep 2007 00:32:43 GMT

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

Ilya Berezhniuk commented on HARMONY-4631:
------------------------------------------

I've detected that both results (13 total failures and 170 total failures) can be fetched
with the same environment settings. For some reasons consequent identical runs can produce
different results.

Moreover, I've reproduced both results when running jdtdebug suite from Eclipse GUI (see http://wiki.apache.org/harmony/Eclipse_Unit_Tests_Pass_on_DRLVM#How_to_run_EUT_individual).
When I left the tests to execute freely, the result was 13 failures. When I dragged windows,
or did some another actions consuming CPU time, the tests started to fail.

It seems to me that child Eclipse instance creates a project and compiles test classes. When
compilation is unsuccessful for some reason, then all tests requiring compiled test classes
become failed. It clarify why all these tests fail (or not fail) together at the same time.

This situation with different results depending on CPU usage is not ret reproducible on RI.
I can see following possible reasons:
- Harmony unhides some unreasonable timings or a kind of race condition in Eclipse;
- It's intermittent Harmony problem with project creation/compilation (or with waiting for
the result of compilation).

> [drlvm][EUT] 126 jdtdebug tests failed w/ due to suspension issue
> -----------------------------------------------------------------
>
>                 Key: HARMONY-4631
>                 URL: https://issues.apache.org/jira/browse/HARMONY-4631
>             Project: Harmony
>          Issue Type: Bug
>         Environment: Windows x86
>            Reporter: Vladimir Beliaev
>
> 126 jdtdebug tests from EUT3.2 failed due to "Program did not suspend, launch terminated"
issue.
> Issue is reproducible on r565552.
> For example:
> Testcase: org.eclipse.jdt.debug.tests.core.LaunchTests.testUnregisteredLaunch:
> junit.framework.AssertionFailedError: Program did not suspend, launch terminated.
> 	at org.eclipse.jdt.debug.tests.AbstractDebugTest.launchAndWait(AbstractDebugTest.java:265)
>                      <skipped...>
> To reproduce the issue (note: do not use cygwin's unzip):
> 1. unzip eclipse-Automated-Tests-3.2.zip (patched version), enter eclipse-testing, unzip
eclipse-junit-tests-M20060629-1905.zip
> 2. unzip eclipse-SDK-3.2-win32.zip to this eclipse-testing saying "yes" for all overridings

> 3. execute the script:
> @echo off 
> set JAVA_HOME=<windows path to your Harmony JDK snapshot>
> set PATH=%JAVA_HOME%\bin;%PATH% 
> set CMD=
> set CMD=%CMD% java
> set CMD=%CMD% -showversion 
> set CMD=%CMD% -jar eclipse\startup.jar 
> set CMD=%CMD% -application org.eclipse.test.uitestapplication 
> set CMD=%CMD% -dev bin 
> set CMD=%CMD% -data workspace 
> set CMD=%CMD% formatter=org.apache.tools.ant.taskdefs.optional.junit.XMLJUnitResultFormatter,log.xml

> set CMD=%CMD% -testpluginname org.eclipse.jdt.debug.tests
> set CMD=%CMD% -classname org.eclipse.jdt.debug.tests.AutomatedSuite
> echo %CMD% 
> %CMD%
> Results:
> check the resulted log.xml.

-- 
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