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/04/18 10:46:15 UTC

[jira] Created: (HARMONY-3690) [drlvm][build][test] having "shared" X-lists is required

[drlvm][build][test] having "shared" X-lists is required
--------------------------------------------------------

                 Key: HARMONY-3690
                 URL: https://issues.apache.org/jira/browse/HARMONY-3690
             Project: Harmony
          Issue Type: Sub-task
          Components: DRLVM
         Environment: any
            Reporter: Vladimir Beliaev


DLRVM tests X-lists are platform & Execution Engine specific. Still there are tests that fail on all platforms or all configurations. Such tests are duplicated in all X-lists (47 X-lists currently).

It worth doing something with these 47 X-lists. For example, the "shared" X-list can be created. Like:

exclude.drlvm_<testsuite> - these tests are excluded for all architectures, OS, EE
exclude.drlvm_<testsuite>.<arch> - these tests are excluded for all OS, EE on specified architecture. Note that I've swapped <arch> & <OS>.
exclude.drlvm_<testsuite>.<arch>.<OS> 
exclude.drlvm_<testsuite>.<arch>.<OS> .<em>

Thanks
Vladimir Beliaev

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


[jira] Updated: (HARMONY-3690) [drlvm][build][test] having "shared" X-lists is required

Posted by "Vladimir Beliaev (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HARMONY-3690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vladimir Beliaev updated HARMONY-3690:
--------------------------------------

    Priority: Minor  (was: Major)

> [drlvm][build][test] having "shared" X-lists is required
> --------------------------------------------------------
>
>                 Key: HARMONY-3690
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3690
>             Project: Harmony
>          Issue Type: Sub-task
>          Components: DRLVM
>         Environment: any
>            Reporter: Vladimir Beliaev
>            Priority: Minor
>
> DLRVM tests X-lists are platform & Execution Engine specific. Still there are tests that fail on all platforms or all configurations. Such tests are duplicated in all X-lists (47 X-lists currently).
> It worth doing something with these 47 X-lists. For example, the "shared" X-list can be created. Like:
> exclude.drlvm_<testsuite> - these tests are excluded for all architectures, OS, EE
> exclude.drlvm_<testsuite>.<arch> - these tests are excluded for all OS, EE on specified architecture. Note that I've swapped <arch> & <OS>.
> exclude.drlvm_<testsuite>.<arch>.<OS> 
> exclude.drlvm_<testsuite>.<arch>.<OS> .<em>
> Thanks
> Vladimir Beliaev

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


[jira] Closed: (HARMONY-3690) [drlvm][build][test] having "shared" X-lists is required

Posted by "Vladimir Beliaev (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HARMONY-3690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vladimir Beliaev closed HARMONY-3690.
-------------------------------------


> [drlvm][build][test] having "shared" X-lists is required
> --------------------------------------------------------
>
>                 Key: HARMONY-3690
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3690
>             Project: Harmony
>          Issue Type: Sub-task
>          Components: DRLVM
>         Environment: any
>            Reporter: Vladimir Beliaev
>            Priority: Minor
>
> DLRVM tests X-lists are platform & Execution Engine specific. Still there are tests that fail on all platforms or all configurations. Such tests are duplicated in all X-lists (47 X-lists currently).
> It worth doing something with these 47 X-lists. For example, the "shared" X-list can be created. Like:
> exclude.drlvm_<testsuite> - these tests are excluded for all architectures, OS, EE
> exclude.drlvm_<testsuite>.<arch> - these tests are excluded for all OS, EE on specified architecture. Note that I've swapped <arch> & <OS>.
> exclude.drlvm_<testsuite>.<arch>.<OS> 
> exclude.drlvm_<testsuite>.<arch>.<OS> .<em>
> Thanks
> Vladimir Beliaev

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


[jira] Resolved: (HARMONY-3690) [drlvm][build][test] having "shared" X-lists is required

Posted by "Vladimir Beliaev (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HARMONY-3690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vladimir Beliaev resolved HARMONY-3690.
---------------------------------------

    Resolution: Won't Fix

The passed year showed that lack of this feature actually does not hurt. So the right way to do not track it anymore and close as WON'T FIX.

> [drlvm][build][test] having "shared" X-lists is required
> --------------------------------------------------------
>
>                 Key: HARMONY-3690
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3690
>             Project: Harmony
>          Issue Type: Sub-task
>          Components: DRLVM
>         Environment: any
>            Reporter: Vladimir Beliaev
>            Priority: Minor
>
> DLRVM tests X-lists are platform & Execution Engine specific. Still there are tests that fail on all platforms or all configurations. Such tests are duplicated in all X-lists (47 X-lists currently).
> It worth doing something with these 47 X-lists. For example, the "shared" X-list can be created. Like:
> exclude.drlvm_<testsuite> - these tests are excluded for all architectures, OS, EE
> exclude.drlvm_<testsuite>.<arch> - these tests are excluded for all OS, EE on specified architecture. Note that I've swapped <arch> & <OS>.
> exclude.drlvm_<testsuite>.<arch>.<OS> 
> exclude.drlvm_<testsuite>.<arch>.<OS> .<em>
> Thanks
> Vladimir Beliaev

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