You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Vladimir Beliaev (JIRA)" <ji...@apache.org> on 2007/10/22 21:20:50 UTC
[jira] Created: (HARMONY-5000) [buildtest][eut] need to run suites
one by one
[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
Reporter: Vladimir Beliaev
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HARMONY-5000) [buildtest][eut] need to run
suites one by one
Posted by "Vladimir Beliaev (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-5000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549481 ]
Vladimir Beliaev commented on HARMONY-5000:
-------------------------------------------
Fortunately 2 of 4 tested suites failed, and <for> stopped the ant run (w/o summary report generation) as:
Keepgoing execution: 2 of 4 iterations failed.
Looks like I do not get the <for> semantic clear enough. I've removed the patches - more testing is required...
> [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
>
> 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.
[jira] Updated: (HARMONY-5000) [buildtest][eut] need to run suites
one by one
Posted by "Vladimir Beliaev (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-5000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Beliaev updated HARMONY-5000:
--------------------------------------
Attachment: (was: 01-H5000.sh)
> [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
> Attachments: 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.
[jira] Commented: (HARMONY-5000) [buildtest][eut] need to run
suites one by one
Posted by "Stepan Mishura (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (HARMONY-5000) [buildtest][eut] need to run suites
one by one
Posted by "Vladimir Beliaev (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-5000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Beliaev updated HARMONY-5000:
--------------------------------------
Attachment: 02-H5000.patch
I've added zobie killer for linux & reattached the patch.
> [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.
[jira] Updated: (HARMONY-5000) [buildtest][eut] need to run suites
one by one
Posted by "Vladimir Beliaev (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-5000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Beliaev updated HARMONY-5000:
--------------------------------------
Attachment: (was: 02-H5000.patch)
> [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
>
> 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.
[jira] Commented: (HARMONY-5000) [buildtest][eut] need to run
suites one by one
Posted by "Vladimir Beliaev (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-5000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550975 ]
Vladimir Beliaev commented on HARMONY-5000:
-------------------------------------------
Stepan, could you get this committed, please?
> [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
> 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.
[jira] Closed: (HARMONY-5000) [buildtest][eut] need to run suites
one by one
Posted by "Vladimir Beliaev (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-5000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Beliaev closed HARMONY-5000.
-------------------------------------
> [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.
[jira] Resolved: (HARMONY-5000) [buildtest][eut] need to run suites
one by one
Posted by "Stepan Mishura (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (HARMONY-5000) [buildtest][eut] need to run suites
one by one
Posted by "Vladimir Beliaev (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-5000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Beliaev updated HARMONY-5000:
--------------------------------------
Attachment: 02-H5000.patch
01-H5000.sh
Ok, the being copied "eclipse-testing/results" directory may be missed if the run suite is skip (say, because of it requires J2SE6.0). So su ch a copying must have failonerror="false" set - fixed now.
Note that the patch contains a placeholder for zomby killer module which is not a subject of this JIRA.
> [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
> 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.
[jira] Updated: (HARMONY-5000) [buildtest][eut] need to run suites
one by one
Posted by "Vladimir Beliaev (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-5000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Beliaev updated HARMONY-5000:
--------------------------------------
Patch Info: [Patch Available]
> [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
> 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.
[jira] Assigned: (HARMONY-5000) [buildtest][eut] need to run suites
one by one
Posted by "Stepan Mishura (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-5000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stepan Mishura reassigned HARMONY-5000:
---------------------------------------
Assignee: Stepan Mishura
> [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.
[jira] Updated: (HARMONY-5000) [buildtest][eut] need to run suites
one by one
Posted by "Vladimir Beliaev (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-5000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Beliaev updated HARMONY-5000:
--------------------------------------
Attachment: 02-H5000.patch
01-H5000.sh
Here is the patch. In short its idea is:
1. "summary-reporter" is renamed to "utils", because a new utility class has been added
2. build.xml extracts the list of suites from eclipse-testing/test.xml with the simple SAX parser. This list is stored to eclipse-testing/eut.suites.run.properties file defining "tests.list" property.
3. build.xml runs the EUT suites one by one where the suites are defined with "tests" property (as previsoly, the "," separator must be used) or extracted from eclipse-testing/test.xml (if "tests" is undefined or empty).
The changes relate to this 3 steps, I hope most of them I either readable or well commented.
Thanks
Vladimir Beliaev
> [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
> 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.
[jira] Updated: (HARMONY-5000) [buildtest][eut] need to run suites
one by one
Posted by "Vladimir Beliaev (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-5000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Beliaev updated HARMONY-5000:
--------------------------------------
Attachment: (was: 02-H5000.patch)
> [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
>
>
> 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.
[jira] Commented: (HARMONY-5000) [buildtest][eut] need to run
suites one by one
Posted by "Vladimir Beliaev (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (HARMONY-5000) [buildtest][eut] need to run suites
one by one
Posted by "Vladimir Beliaev (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-5000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Beliaev updated HARMONY-5000:
--------------------------------------
Component/s: build - test - ci
Estimated Complexity: Moderate
Description:
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
Environment: any
> [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
>
> 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.