You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Alexey Varlamov (JIRA)" <ji...@apache.org> on 2007/03/06 10:50:24 UTC

[jira] Closed: (HARMONY-3303) [drlvm][test] EE to run EHWA is configured by ehwa.test.mode parameter, but all other test are controlled by test.mode parameter

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

Alexey Varlamov closed HARMONY-3303.
------------------------------------

    Resolution: Fixed

Thanks for the update, applied at r515047

> [drlvm][test] EE to run EHWA is configured by ehwa.test.mode parameter, but all other test are controlled by test.mode parameter
> --------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HARMONY-3303
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3303
>             Project: Harmony
>          Issue Type: Improvement
>          Components: DRLVM
>         Environment: All
>            Reporter: Pavel Pervov
>         Assigned To: Alexey Varlamov
>            Priority: Minor
>         Attachments: ehwa.test.mode.patch
>
>
> EHWA VM test scenario is being run on all three execution engines. But the switch controlling this has name which differs from all other test scenarios: all other tests uses "test.mode" while EHWA uses "ehwa.test.mode". I do not see any reason behind this and will attach the patch which unifies these two.

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