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.
Created attachment 1809690[details]
build.log.xz
This is the clang variant of bug 1988288. Different tests fail in recent builds on s390x:
FAIL: Clang :: Modules/embed-files-compressed.cpp (8052 of 29120)
FAIL: Clang :: Modules/stress1.cpp (8330 of 29120)
Setting SOURCE_DATE_EPOCH in the environment is supposed to turn of s390x hardware acceleration, and RPM should do that during the %check phase, too. It's not clear to me why this is not effective.
I'm closing this bug as WONTFIX. The test that is failing is producing correct output even though it is not identical to the expected output. I don't think it's worth doing a whole new build just to fix a test case. We will 'fix' this the next time we do a build for some other bug, but since there is nothing for QE to test here I don't think it is worth tracking this in a bug any more.