Bug 1310061
Summary: | Problem with running SPECjvm2008 benchmark | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Kamil Kolakowski <kkolakow> | ||||
Component: | java-1.7.0-openjdk | Assignee: | Andrew Dinn <adinn> | ||||
Status: | CLOSED ERRATA | QA Contact: | Lukáš Zachar <lzachar> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | high | ||||||
Version: | 7.2 | CC: | adinn, ahughes, aph, dbhole, emcnabb, jbastian, jhladky, jvanek | ||||
Target Milestone: | rc | ||||||
Target Release: | --- | ||||||
Hardware: | aarch64 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | java-1.7.0-openjdk-1.7.0.95-2.6.4.3.el7 | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2016-11-03 22:59:12 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Kamil Kolakowski
2016-02-19 11:03:24 UTC
Alternately you can install the benchmark from Beaker repo: yum -y install performance-performance-SPECjvm2008-test-certification.noarch I will attach the rpm file to this BZ as well. After the installation do the following: cd /mnt/tests/performance/SPECjvm2008-test/certification/ Run benchmark with on ARM server ./runtest.sh After roughly 15 minutes go to cd SPECjvm2008/results and run find ./ -name "*error*" If you see file like this one compiler.compiler.bt2.i1.op1.error.log with ERROR: compiler exit code: 4 then you have reproduced the issue. We believe it's a bug in java. Please feel free to ping either kkolakow or jhladky if you need to get access to ARM server or you require help to reproduce the problem. Thanks Jirka Created attachment 1128519 [details]
rpm file with benchmark
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-2140.html |