Return-Path: 
 <commits-return-29987-apmail-harmony-commits-archive=harmony.apache.org@harmony.apache.org>
Delivered-To: apmail-harmony-commits-archive@www.apache.org
Received: (qmail 55261 invoked from network); 9 Mar 2007 11:31:16 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 9 Mar 2007 11:31:16 -0000
Received: (qmail 18218 invoked by uid 500); 9 Mar 2007 11:31:24 -0000
Delivered-To: apmail-harmony-commits-archive@harmony.apache.org
Received: (qmail 18093 invoked by uid 500); 9 Mar 2007 11:31:23 -0000
Mailing-List: contact commits-help@harmony.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:commits-help@harmony.apache.org>
List-Unsubscribe: <mailto:commits-unsubscribe@harmony.apache.org>
List-Post: <mailto:commits@harmony.apache.org>
List-Id: <commits.harmony.apache.org>
Reply-To: dev@harmony.apache.org
Delivered-To: mailing list commits@harmony.apache.org
Received: (qmail 18076 invoked by uid 99); 9 Mar 2007 11:31:23 -0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Mar 2007 03:31:23 -0800
Received: from brutus (localhost [127.0.0.1])
	by brutus.apache.org (Postfix) with ESMTP id 6CD5A714057
	for <commits@harmony.apache.org>; Fri,  9 Mar 2007 03:30:24 -0800 (PST)
Message-ID: <15740184.1173439824443.JavaMail.root@brutus>
Date: Fri, 9 Mar 2007 03:30:24 -0800 (PST)
From: "Stepan Mishura (JIRA)" <jira@apache.org>
To: commits@harmony.apache.org
Subject: [jira] Resolved: (HARMONY-3319) [jdktools][jpda] JDWP unit tests
 fail with timeout
In-Reply-To: <8468049.1173256944263.JavaMail.root@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org


     [ https://issues.apache.org/jira/browse/HARMONY-3319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stepan Mishura resolved HARMONY-3319.
-------------------------------------

    Resolution: Fixed

Thanks Ivan - the modified patch was applied to JPDA module at r516374 - I've updated ant script to exclude forkmode=ones for jpda tests. Please let me know if you disagree with my modifications.


> [jdktools][jpda] JDWP unit tests fail with timeout
> --------------------------------------------------
>
>                 Key: HARMONY-3319
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3319
>             Project: Harmony
>          Issue Type: Bug
>          Components: JDK
>         Environment: Windows/ia32, Linux/ia32, Harmony-jdk-r515478
>            Reporter: Ivan Popov
>         Assigned To: Stepan Mishura
>         Attachments: jpda_build.patch
>
>
> JDWP unit tests from JPDA component started with ant build usually fail with timeout:
> <...>   
>     [junit] TEST org.apache.harmony.jpda.tests.jdwp.ReferenceType.GetValues003Test FAILED
>     [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 9.578 sec
>     [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 9.543 sec
>     [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 9.537 sec
>     [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec
>     [junit] Tests FAILED (timeout)
> <...>
> full-report:
> [junitreport] [Fatal Error] :-1:-1: Premature end of file.
> [junitreport] The file .../trunk/working_jdktools/build/test_report/TEST-org.apache.harmony.jpda.tests.jdwp.ReferenceType.InterfacesTest.xml is not a valid XML document. It is possibly corrupted.
> The problem is in default timeout (120000 milliseconds, or 15 minutes) specified for junit task in 'timeout" option:
>                timeout="${hy.test.timeout}"
> JUnit task reference reads for this option:
>   Cancel the individual tests if they don't finish in the given time (measured in milliseconds). Ignored if fork is disabled.
> However, it seems that this option is applied to the whole tests set specified in <batchtest> item.  All JDWP tests are specified in a single <batchtest> and their execution usually exceeds 15 minutes, so junit task cancels them with timeout.
> There are several "long-running" tests, each takes about 1 minute. These tests can be moved to a separate <batchtest> item  to satisfy the default timeout.

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