Mailing-List: contact commits-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Message-ID: <24854861.1190627511296.JavaMail.jira@brutus>
Date: Mon, 24 Sep 2007 02:51:51 -0700 (PDT)
From: "Vladimir Beliaev (JIRA)" <jira@apache.org>
To: commits@harmony.apache.org
Subject: [jira] Updated: (HARMONY-4835) [buildtest][eut] Expected Crashes
 must be considered by summary reporter
In-Reply-To: <229936.1190316284582.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Vladimir Beliaev updated HARMONY-4835:
--------------------------------------

    Patch Info: [Patch Available]

> [buildtest][eut] Expected Crashes must be considered by summary reporter
> ------------------------------------------------------------------------
>
>                 Key: HARMONY-4835
>                 URL: https://issues.apache.org/jira/browse/HARMONY-4835
>             Project: Harmony
>          Issue Type: Bug
>          Components: build - test - ci
>         Environment: any
>            Reporter: Vladimir Beliaev
>         Attachments: H4835.patch
>
>
> There are still some EUT suites which crashes due to lack of Harmony functionality. 
> So such crashes is not a subject of bug fixing toward DRLVM stability. 
> So it is ok to add such suite to Expected Failure List (EFL). For example:
>     # Invalid: JVMPI is unsupported - deprecated functionality
>     org.eclipse.jdt.ui.tests.LeakTestSuite
> So the Summary Reporter should consider such records in EFL and generate the correct summary.

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