Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at

Bug 993919

Summary: Java segfaults when building junitperf only on ARM
Product: [Fedora] Fedora Reporter: Mat Booth <mat.booth>
Component: java-1.7.0-openjdkAssignee: Deepak Bhole <dbhole>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: ahughes, dbhole, jerboaa, jvanek, omajid
Target Milestone: ---   
Target Release: ---   
Hardware: arm   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-06 14:09:59 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:
Bug Depends On:    
Bug Blocks: 245418    
Description Flags
junitperf koji build.log
junitperf koji root.log none

Description Mat Booth 2013-08-06 13:13:09 UTC
Description of problem:

Try rebuilding the junitperf package, master branch from source, on an ARM builder. Java segfaults every time.

Version-Release number of selected component (if applicable):

ant                        noarch    1.9.2-3.fc20
ant-junit                  noarch    1.9.2-3.fc20
java-1.7.0-openjdk-devel   armv7hl   1:
javapackages-tools         noarch    2.0.1-1.fc20
junit                      noarch    4.11-5.fc20

The workaround is to continue submitting builds until koji randomly selects a non-ARM builder.

Comment 1 Mat Booth 2013-08-06 13:13:55 UTC
Created attachment 783320 [details]
junitperf koji build.log

Comment 2 Mat Booth 2013-08-06 13:15:10 UTC
Created attachment 783321 [details]
junitperf koji root.log

Comment 3 Mat Booth 2013-08-06 14:09:59 UTC

*** This bug has been marked as a duplicate of bug 991712 ***