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 1238567

Summary: perl-5.16.3-285.el7 FTBFS on ppc64le: Failed test 'is 533.783783783784 within 0.4 of estimate (910.35)' at ../lib/Benchmark.t line 93
Product: Red Hat Enterprise Linux 7 Reporter: Petr Pisar <ppisar>
Component: perlAssignee: Petr Pisar <ppisar>
Status: CLOSED ERRATA QA Contact: Martin Kyral <mkyral>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.2CC: isenfeld, jorton, lmiksik, mkyral
Target Milestone: rcKeywords: Patch, Regression
Target Release: ---   
Hardware: ppc64le   
OS: Unspecified   
URL: https://brewweb.devel.redhat.com/taskinfo?taskID=9453529
Whiteboard:
Fixed In Version: perl-5.16.3-286.el7 Doc Type: Bug Fix
Doc Text:
Due to a Benchmark sub-test sensitive to CPU scheduling and thus prone to random failures, the Perl test suite failed. Consequently, it was impossible to build perl on the little-endian variant of IBM Power Systems architecture. This update removes the problematic sub-test, and perl builds correctly on the mentioned platform.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-19 12:59: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: 1238472    
Attachments:
Description Flags
Upstream fix ported to 5.16.3 none

Description Petr Pisar 2015-07-02 07:41:29 UTC 
Perl test suite fails when building on ppc64le:

#   Failed test 'is 533.783783783784 within 0.4 of estimate (910.35)'
#   at ../lib/Benchmark.t line 93.
#     '0.705465822784811'
#         <=
#     '0.4'
#   in_threesecs     = 2813
#   in_threesecs_adj = 2731.06796116505
#   cpu3             = 3.09
#   sys3             = 0
#   estimate         = 910.35
#   in_onesec        = 790
#   in_onesec_adj    = 533.783783783784
#   cpu1             = 1.48
#   sys1             = 0
Comment 3 Petr Pisar 2015-07-02 09:10:21 UTC 
Upstream removed the subtest because it was proved to be to fragile:

commit 9eba9e102c2f8c2ec41a50f4bbe6b09a64dddd31
Author: David Mitchell <davem>
Date:   Fri Jul 19 23:10:50 2013 +0100

    Benchmark.t: remove CPU-speed-sensitive test
    
    Benchmark.t has been randomly failing test 15 in smokes for ages.
    This is the one that checks that a loop run 3*N times burns approximately
    3 times more CPU than when run just N times.
    
    For the last month the test has included a calibration loop and test,
    which does much the same thing, but without using any code from
    Benchmark.pm. This has failed just as much, which confirms that its an
    issue with the smoke host (such as a variable speed CPU or whatever),
    rather than any flaw in the Benchmark.pm library logic.
    
    So just remove the calibration loop and the dodgy test.
Comment 4 Petr Pisar 2015-07-02 10:13:08 UTC 
Created attachment 1045451 [details]
Upstream fix ported to 5.16.3
Comment 9 errata-xmlrpc 2015-11-19 12:59: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/RHBA-2015-2113.html