You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Aleksey Shipilev (JIRA)" <ji...@apache.org> on 2008/11/24 00:11:44 UTC
[jira] Created: (HARMONY-6026) Multiple bugs/crashes on DaCapo
while varying JIT configurations
Multiple bugs/crashes on DaCapo while varying JIT configurations
----------------------------------------------------------------
Key: HARMONY-6026
URL: https://issues.apache.org/jira/browse/HARMONY-6026
Project: Harmony
Issue Type: Bug
Components: DRLVM
Affects Versions: 5.0M7
Environment: Gentoo x86, Harmony M7, DaCapo MR2
Reporter: Aleksey Shipilev
Attachments: test-emconfs.tar.gz
This is the contribution of test cases which were failed while varying RVM command line parameters. Parameters were swizzled by custom-made GA framework developed for getting my MSc degree. Though this result is not the primary, it really makes the fuzzy testing of RVM and effectively produces the reliability test.
To use the materials, one should download test-emconfs.tar.gz, unpack it and explore the test-emconfs/ folder.
The failures were classified by benchmark and the type of crash occured. Each report file names as ${benchmark}${type_of_crash}${N}.report, where ${benchmark} is the DaCapo test on which the failure was observed, and ${type_of_crash} is the type of failure occured, as follows:
a. (3195 cases) "GPF", General protection fault signal caught
b. (1237 cases) "SpillGen", "Jitrino crashed // SpillGen failed" received
c. (496 cases) "IMSE", java.lang.IllegalMonitorStateException caught
d. (270 cases) "JIT-LIR", "JIT helper is not supported in LIR" was received
e. (260 cases) "ABORT", Abort signal caught
f. (124 cases) "unknown", not-classified failures, hangups, timeouts, etc.
g. (95 cases) "NPE", java.lang.NullPointerException caught
h. (39 cases) "Dacapo-failed", DaCapo has failed the verification
There are totally 5716 test cases. Not all of them were verified to reproduce, it's just the excerpt from search log.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HARMONY-6026) Multiple bugs/crashes on DaCapo
while varying JIT configurations
Posted by "Aleksey Shipilev (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-6026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aleksey Shipilev updated HARMONY-6026:
--------------------------------------
Attachment: test-emconfs.tar.gz
test-emconfs.tar.gz
Test emconfs.
> Multiple bugs/crashes on DaCapo while varying JIT configurations
> ----------------------------------------------------------------
>
> Key: HARMONY-6026
> URL: https://issues.apache.org/jira/browse/HARMONY-6026
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Affects Versions: 5.0M7
> Environment: Gentoo x86, Harmony M7, DaCapo MR2
> Reporter: Aleksey Shipilev
> Attachments: test-emconfs.tar.gz
>
>
> This is the contribution of test cases which were failed while varying RVM command line parameters. Parameters were swizzled by custom-made GA framework developed for getting my MSc degree. Though this result is not the primary, it really makes the fuzzy testing of RVM and effectively produces the reliability test.
> To use the materials, one should download test-emconfs.tar.gz, unpack it and explore the test-emconfs/ folder.
> The failures were classified by benchmark and the type of crash occured. Each report file names as ${benchmark}${type_of_crash}${N}.report, where ${benchmark} is the DaCapo test on which the failure was observed, and ${type_of_crash} is the type of failure occured, as follows:
> a. (3195 cases) "GPF", General protection fault signal caught
> b. (1237 cases) "SpillGen", "Jitrino crashed // SpillGen failed" received
> c. (496 cases) "IMSE", java.lang.IllegalMonitorStateException caught
> d. (270 cases) "JIT-LIR", "JIT helper is not supported in LIR" was received
> e. (260 cases) "ABORT", Abort signal caught
> f. (124 cases) "unknown", not-classified failures, hangups, timeouts, etc.
> g. (95 cases) "NPE", java.lang.NullPointerException caught
> h. (39 cases) "Dacapo-failed", DaCapo has failed the verification
> There are totally 5716 test cases. Not all of them were verified to reproduce, it's just the excerpt from search log.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.