Bug 1064063 - Test suite failure: tst-mqueue5
Summary: Test suite failure: tst-mqueue5
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: glibc   
(Show other bugs)
Version: 7.0
Hardware: ppc64
OS: Linux
Target Milestone: rc
: ---
Assignee: Martin Sebor
QA Contact: Arjun Shankar
Keywords: Patch
Depends On:
Blocks: 1297579 1313485 1110700
TreeView+ depends on / blocked
Reported: 2014-02-11 22:28 UTC by Patsy Franklin
Modified: 2016-11-03 08:21 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-11-03 08:21:20 UTC
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:2573 normal SHIPPED_LIVE Low: glibc security, bug fix, and enhancement update 2016-11-03 12:05:56 UTC

Description Patsy Franklin 2014-02-11 22:28:18 UTC
Description of problem:
tst-queue5 fails on ppc64

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

How reproducible:
Always on RHEL 7.0

Steps to Reproduce:
1.  see build log

Comment 11 Florian Weimer 2016-01-15 19:06:08 UTC
Upstream patch: https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=a3e5b4feeb54cb92657ec2bc6d9be1fcef9e8575

I had a ppc64 RHEL 7.3 system in Beaker which showed consistent failures when the test was run in isolation; glibc master was compiled for ppc (32-bit).  That went away when I applied this fix, and the failure reappeared when I unapplied it.  There might other be issues with this test, but the upstream patch is a clear improvement.

Comment 17 errata-xmlrpc 2016-11-03 08:21:20 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.


Note You need to log in before you can comment on or make changes to this bug.