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

[jira] Created: (HARMONY-4995) [drlvm][jit] VM crash in struts tests

[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


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.


[jira] Reopened: (HARMONY-4995) [drlvm][jit] VM crash in struts tests

Posted by "Alexei Zakharov (JIRA)" <ji...@apache.org>.
     [ 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.


[jira] Closed: (HARMONY-4995) [drlvm][jit] VM crash in struts tests

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

Alexei Zakharov closed HARMONY-4995.
------------------------------------


Thanks everybody.

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


[jira] Updated: (HARMONY-4995) [drlvm][jit] VM crash in struts tests

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

Yuri Dolgov updated HARMONY-4995:
---------------------------------

    Attachment: HARMONY-4995.patch

Issue is due to branch translator could create situation when true and false branches point to the same basic block. To solve the issue additional analysis was added to DCE implementation.
Patch for the issue attached.


> [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
>         Attachments: assertion_failed_error.jpg, HARMONY-4995.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.


[jira] Resolved: (HARMONY-4995) [drlvm][jit] VM crash in struts tests

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

Alexei Zakharov resolved HARMONY-4995.
--------------------------------------

    Resolution: Fixed

The problem is not reproducible anymore. Issue closed.

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


[jira] Commented: (HARMONY-4995) [drlvm][jit] VM crash in struts tests

Posted by "Alexei Zakharov (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HARMONY-4995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536711 ] 

Alexei Zakharov commented on HARMONY-4995:
------------------------------------------

I 'm not really sure it is required for screenshots. But anyway I grant all rights for the attached screenshot to Apache Software Foundation. 

> [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
>         Attachments: assertion_failed_error.jpg
>
>
> 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.


[jira] Updated: (HARMONY-4995) [drlvm][jit] VM crash in struts tests

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

Yuri Dolgov updated HARMONY-4995:
---------------------------------

    Attachment: HARMONY-4995_2.patch

A case for fals/true branches with the same diestination added

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


[jira] Commented: (HARMONY-4995) [drlvm][jit] VM crash in struts tests

Posted by "Yuri Dolgov (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HARMONY-4995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541838 ] 

Yuri Dolgov commented on HARMONY-4995:
--------------------------------------

Alexey, struts tests fail due to another problem and I have already created a JIRA (HARMONY-5096) to track this. And actualy I've already prepared a patch for it. It's not commited yet, but you could try to test it if you want to.

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


[jira] Updated: (HARMONY-4995) [drlvm][jit] VM crash in struts tests

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

Alexei Zakharov updated HARMONY-4995:
-------------------------------------

    Attachment: assertion_failed_error.jpg

assertion failed screenshot

> [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
>         Attachments: assertion_failed_error.jpg
>
>
> 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.


[jira] Assigned: (HARMONY-4995) [drlvm][jit] VM crash in struts tests

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

Alexey Varlamov reassigned HARMONY-4995:
----------------------------------------

    Assignee: Alexey Varlamov

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


[jira] Resolved: (HARMONY-4995) [drlvm][jit] VM crash in struts tests

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

Alexey Varlamov resolved HARMONY-4995.
--------------------------------------

    Resolution: Fixed

Yuri, thanks for the patch, applied at revision: 589594. A few notes:
- added code used tabs for indentation, please ensure your IDE is configured to indent with spaces;
- it did not compile on GCC until "s/Edge::Kind::Kind_/Edge::Kind_/g";
- would be nice to diff against svn module root which is "working_vm" - to save committers keystrokes ;)

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