harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexei Zakharov (JIRA)" <j...@apache.org>
Subject [jira] Reopened: (HARMONY-4995) [drlvm][jit] VM crash in struts tests
Date Mon, 12 Nov 2007 16:43:50 GMT

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

Alexei Zakharov reopened HARMONY-4995:
--------------------------------------


It should be mentioned in spite of the fact that VM crash has disappeared struts scenario
still fails. So it looks like  the issue is more tricky. The last time I see struts scenario
passing was before the above-mentioned revision 584097. JIRA.was reopened.

> [drlvm][jit] VM crash in struts tests
> -------------------------------------
>
>                 Key: HARMONY-4995
>                 URL: https://issues.apache.org/jira/browse/HARMONY-4995
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>         Environment: Win32
>            Reporter: Alexei Zakharov
>            Assignee: Alexey Varlamov
>         Attachments: assertion_failed_error.jpg, HARMONY-4995.patch, HARMONY-4995_2.patch
>
>
> It looks like the patch from HARMONY-4875 ([drlvm][jit] Harmony has negative scalability
in client mode, committed at the revision 584097)  introduced a regression in Struts test.
Currently I see the following assertion failed error if I run struts tests on debug DRLVM
build - see attached screenshot. In release mode tests fail with some strange error. However,
everything was fine at the revision 584088. 
> Due to complex nature of struts tests it is very hard to extract a small test case from
it. Below are exact steps to reproduce the original error. Hope this helps.
> 1. Check out our BTI source tree and configure it according to README
> 2. Place the following lines into buildtest\branches\2.0\framework.local.properties
> struts_test.parameters.required.req.test.java.home=%DRLVM_HOME%
> struts_test.parameters.required.req.driver.java.home=%RI_JDK_HOME%
> 3. Your ANT_OPTS environment variable should contain valid proxy host and port information
at this step
> 4. rm required-parameters.properties
> 5. ant -Dtest.suites=struts_test setup
> 6. ant -Dtest.suites=struts_test run
> 7. BAH!

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