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.

Description of problem:
Make check fails on ppc64le

Version-Release number of selected component (if applicable):
orc-0.4.22-3.el7.ppc64le

How reproducible:
Always

Steps to Reproduce:
1. Run make check in orc's buildroot

Actual results:
PASS: abi
FAIL: test-limits


Expected results:
All tests pass (same as on x86_64 and ppc64)

Additional info:
See full test log at https://desktopqe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/desktop-orc-RHEL-7.2-2-runtest/20/artifact/testresults-FAKE/Test00_upstream-testset.log

Can I get access to the machine to debug the issue?

OK, it's not really an error in ORC, the unit test just doesn't deal well with the fact that there is no backend for PPC64.

Not exactly an easy fix. We need a way to clear the error on the program so that the unit test can ignore the compilation error and then check the real error (adding too many constants).

I have a simple fix pushed upstream, I can apply this to the rhel-7.2 package.

Verified on orc-0.4.22-4.el7.ppc64le

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-2116.html