[jira] Updated: (HARMONY-4614) [buildtest][eut] EUT3.3 does not understand -XX:vm.assert_dialog=false option

["Vladimir Beliaev (JIRA)" <ji...@apache.org>]

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

Vladimir Beliaev updated HARMONY-4614:
--------------------------------------

    Attachment: HARMONY-4614.patch

The attached patch removes -XX:vm.assert_dialog=false VM argument setting.

It also corrects the EUT3.3 properties access and report results name - the errors found by Alexey Varlamov.

> [buildtest][eut] EUT3.3 does not understand -XX:vm.assert_dialog=false option
> -----------------------------------------------------------------------------
>
>                 Key: HARMONY-4614
>                 URL: https://issues.apache.org/jira/browse/HARMONY-4614
>             Project: Harmony
>          Issue Type: Sub-task
>          Components: build - test - ci
>            Reporter: Vladimir Beliaev
>         Attachments: HARMONY-4614.patch
>
>
> According to EUT3.3 readme.html (same to EUT3.2) one may define extraVMargs property (together with J2SE-5.0 property) to specify the additional running arguments to the Java VM wich should run the tests.
> So one uses this "extraVMargs" property  to set -XX:vm.assert_dialog=false to avoid blocking popup dialogs (on Windows)  to enable automated running.
> Setting 'extraVMargs' for EUT3.2 wookds just fine while EUT3.3 complains like: "unknown VM option 'vm.assert_dialog'". So EUT3.3 either passes this property to "running harness VM" (which is not Harmony DRLVM for now) or process incorrectly -XX: prefix.
> Anyway, since Harmony release build have the default value for vm.assert_dialog equals "false" there is no need to specify this property in EUT3.3 configuration file. The adaptors/parameters.xml file should be updated.
> Thanks
> Vladimir Beliaev

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