harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stepan Mishura (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-5000) [buildtest][eut] need to run suites one by one
Date Thu, 13 Dec 2007 08:17:44 GMT

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

Stepan Mishura commented on HARMONY-5000:
-----------------------------------------

As I understood the description and the patch - the overall target of this update is to make
possible to run 'zombie killer' after each suite. Correct?

IMO the 'original suite build script' (i.e. eclipse-testing/test.xml file) already runs suites
one by one (i.e. prepares env. and forks new VM for each suite)
So from my POV it doesn't make sense to duplicate this logic in our build scripts (that is
turn will make it more complicated). I think we should consider injecting 'zombie killer'
into the 'original suite build script'. This is a hack but IMO it worth it because it can
be implemented in simple and straightforward way - there is a macro ("runTests") in the suite
script that is used for launching each suite. So we can easily patch the build script to make
the macro to invoke target that kills all zombies before launching a suite.

What do you think?


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


Mime
View raw message