You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Stepan Mishura (JIRA)" <ji...@apache.org> on 2007/12/20 08:01:48 UTC

[jira] Resolved: (HARMONY-5000) [buildtest][eut] need to run suites one by one

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

Stepan Mishura resolved HARMONY-5000.
-------------------------------------

    Resolution: Fixed

Thanks Vladimir - the patch was applied to BTI branch 2.0 at r605817.
Please check that the patch was applied as you expected.

> [buildtest][eut] need to run suites one by one
> ----------------------------------------------
>
>                 Key: HARMONY-5000
>                 URL: https://issues.apache.org/jira/browse/HARMONY-5000
>             Project: Harmony
>          Issue Type: Sub-task
>          Components: build - test - ci
>         Environment: any
>            Reporter: Vladimir Beliaev
>            Assignee: Stepan Mishura
>         Attachments: 01-H5000.sh, 02-H5000.patch
>
>
> This corresponds to task #4 in the root JIRA. I.e:
> M3 issues with intermittent suite crashes on Linux (which are not reproducible while running suite as stand along unit) indicates it worth redoing EUT Suites running process to run them one by one, not with the help of single running. 
> I'm not yet sure what way this can be done taking into account the way must be universal for both EUT3.2 and EUT3.3.
> One of the options is to run particular testcase for the plugin with the command like:
>    <harmony java> \ 
>       -data workspace \
>       ...
>      -testpluginname org.eclipse.jdt.core.tests.model \
>      -classname org.eclipse.jdt.core.tests.dom.RunAllTests 
> The list of parameters may be taken from tests/eut/config/eut*.suites.properties file (like what plugin the suite belong too and if this suite requires uitestapplication or coretestapplication).
> Another option is to run particular suite by its name (like "jdtdebug" suite). It is closer to existing one. Still it is not clear what way the list of suites can be obtained (normally it is harcoded in unpacked eclipse-testing/test.xml file).
> Thanks
> Vladimir

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