Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1702247

Summary:	Failed upstream test cases (-z now?)
Product:	Red Hat Developer Toolset	Reporter:	Miloš Prchlík <mprchlik>
Component:	binutils	Assignee:	Nick Clifton <nickc>
Status:	CLOSED ERRATA	QA Contact:	Miloš Prchlík <mprchlik>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	DTS 8.1 RHEL 7	CC:	bgollahe, law, mcermak, mnewsome, mpolacek, ohudlick, tborcin
Target Milestone:	alpha
Target Release:	8.1
Hardware:	aarch64
OS:	Unspecified
Whiteboard:
Fixed In Version:	binutils-2.30-54.el7, binutils-2.30-54.el6	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-11 10:23:50 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:

Description Miloš Prchlík 2019-04-23 10:14:55 UTC

Description of problem:

Recent test run for DTS binutils, following test cases failed:

FAIL: Run ifunc-main with PIE (-z now)
FAIL: Run ifunc-main (-z now)
FAIL: Run pr16467 (-z now)
FAIL: Run pr18808 (-z now)
FAIL: Run pr18841 with libpr18841bn.so (-z now)
FAIL: Run pr18841 with libpr18841b.so

Buildroot archive with remnants of the test lies here: https://beaker.engineering.redhat.com/recipes/6759736/tasks/91344436/logs/buildroot.tgz



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

devtoolset-8-binutils-2.30-53.el7.aarch64


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Nick Clifton 2019-04-24 09:59:55 UTC

Fixed in: binutils-2.30-54.el7

Comment 3 Nick Clifton 2019-04-24 10:02:15 UTC

Also fixed in: binutils-2.30-54.el6

Comment 5 Miloš Prchlík 2019-05-14 11:55:38 UTC

Verified with devtoolset-8-binutils-2.30-54.

Comment 7 errata-xmlrpc 2019-06-11 10:23:50 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://access.redhat.com/errata/RHBA-2019:1451