Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1152896

Summary: build fails on machine with too many cpu cores
Product: Red Hat Enterprise Linux 6 Reporter: Tuomo Soini <tis>
Component: java-1.8.0-openjdkAssignee: Andrew John Hughes <ahughes>
Status: CLOSED ERRATA QA Contact: Lukáš Zachar <lzachar>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.6CC: ahughes, bnater, dbhole, dkutalek, jvanek
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: java-1.8.0-openjdk-1.8.0.65-2.b17.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-10 21:03:05 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:
Bug Depends On:    
Bug Blocks: 1271375    
Attachments:
Description Flags
Proposed patch - honor %_smp_ncpus_max none

Description Tuomo Soini 2014-10-15 07:24:28 UTC
Created attachment 947112 [details]
Proposed patch - honor %_smp_ncpus_max

Description of problem:

rebuild of java-1.8.0-openjdk package fails on a machine with big number of cpu cores.

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

java-1.8.0-openjdk-1.8.0.20-3.b26.el6

How reproducible:

Nearly always, the more cores, the more often random build failures happen.

Actual results:

If build machine has 24 cores build always fail with my limited testing (eight tries).

Comment 2 Deepak Bhole 2014-10-15 13:40:42 UTC
Hi, does the build fail without the patch, or does it just not use the right number of cores?

Comment 3 Tuomo Soini 2014-10-15 20:42:57 UTC
Build fails without patch. With patch and %_smp_ncpus_max 8  build works.

This is work-around only, real problem is in openjdk makefiles.

There is no similar problem with java-1.6.0-openjdk or java-1.7.0-openjdk.

Comment 4 Deepak Bhole 2014-10-16 14:30:29 UTC
Ah, so this is just 8-specific. Jiri, please take a look when you get a chance.

Comment 5 Tuomo Soini 2014-10-16 16:07:00 UTC
Did I say it somehow unclearly?

With 8 cores or less there is no problem.

With 24 cores build fails always without patch and number of cores limited.

Comment 6 Deepak Bhole 2014-10-16 16:08:28 UTC
No you were clear. I meant OpenJDK8 specific :)

Comment 11 errata-xmlrpc 2016-05-10 21:03:05 UTC
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/RHEA-2016-0816.html