harmony-commits mailing list archives

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

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

Vladimir Beliaev commented on HARMONY-5000:
-------------------------------------------

I think that changing eclipse-testing/test.xml is not an option:

1. it requires better undersdanding of this test.xml & I do not have it. Instead what
I did in this patch is that I scripreed in the tests\eut\build.xml the work I always do manually
for double checking CC reported issues - i.e. clean all stuff from previous run, unpack archives
from scratch.

2. test.xml content depends on Eclipse version (say, eut3.2 difers from eut3.3, still "all"
target format is the same & we can use it)

3. the last but the most important - we must keep in mind that EUT is for Eclipse testing,
not for JRE testing. I believe with the stable JRE (say, which does not leave zobies) the
EUT clean-up all of the required resources by itself. Still we can't relay on it while testing
Harmonby with EUT.

So I vote for committing this patch. Let's see if it helps with Harmony/EUT stability on Linux
x86_64.

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