harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Pervov (JIRA)" <j...@apache.org>
Subject [jira] Updated: (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
Date Mon, 05 Mar 2007 15:40:51 GMT

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

Pavel Pervov updated HARMONY-3303:
----------------------------------

    Summary: [drlvm][test] EE to run EHWA is configured by ehwa.test.mode parameter, but all
other test are controlled by test.mode parameter  (was: [drlvm][test])

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


Mime
View raw message