Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1865608 - vmemcache: FTBFS in Fedora rawhide/f33
Summary: vmemcache: FTBFS in Fedora rawhide/f33
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: vmemcache
Version: 33
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Borowski
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F33FTBFS
TreeView+ depends on / blocked
 
Reported: 2020-08-03 21:28 UTC by Fedora Release Engineering
Modified: 2020-08-25 11:46 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-08-25 11:46:20 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
build.log (32.00 KB, text/plain)
2020-08-03 21:28 UTC, Fedora Release Engineering 		no flags Details
root.log (32.00 KB, text/plain)
2020-08-03 21:28 UTC, Fedora Release Engineering 		no flags Details
state.log (963 bytes, text/plain)
2020-08-03 21:28 UTC, Fedora Release Engineering 		no flags Details
View All

Description Fedora Release Engineering 2020-08-03 21:28:00 UTC 
vmemcache failed to build from source in Fedora rawhide/f33

https://koji.fedoraproject.org/koji/taskinfo?taskID=48362338


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_33_Mass_Rebuild
Please fix vmemcache at your earliest convenience and set the bug's status to
ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks,
vmemcache will be orphaned. Before branching of Fedora 34,
vmemcache will be retired, if it still fails to build.

For more details on the FTBFS policy, please visit:
https://fedoraproject.org/wiki/Fails_to_build_from_source
Comment 1 Fedora Release Engineering 2020-08-03 21:28:02 UTC 
Created attachment 1709980 [details]
build.log

file build.log too big, will only attach last 32768 bytes
Comment 2 Fedora Release Engineering 2020-08-03 21:28:03 UTC 
Created attachment 1709981 [details]
root.log

file root.log too big, will only attach last 32768 bytes
Comment 3 Fedora Release Engineering 2020-08-03 21:28:04 UTC 
Created attachment 1709982 [details]
state.log
Comment 4 Jeff Law 2020-08-04 05:48:26 UTC 
There's an LTO component here.  I'll take it for now.
Comment 5 Jeff Law 2020-08-06 20:14:48 UTC 

With LTO, calls to Zalloc within the DSO are turned into calls to calloc.  Why?  Nothing calls util_set_alloc_funcs & its got local scope from the DSO's point of view and thus Malloc is a constant (malloc) and thus Zalloc turns into malloc+memset which is then transformed into calloc).  Those calls to calloc then go into the libc DSO which calls malloc which is satisfied by the libc DSO.

That all bypasses the intercepts set up by the testsuite and as a result the accounting of how much space is allocated vs how much is freed is inaccurate.

What this all means is the test is flawed and it should be intercepting calloc as well.  In the mean time, I'm going to disable LTO for this package.  It's still failing its testsuite, but not due to any LTO issues.  The package maintainer needs to step in a fix the testsuite issues to resolve the FTBFS.
Comment 6 Ben Cotton 2020-08-11 15:14:55 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle.
Changing version to 33.
Comment 7 Adam Borowski 2020-08-25 11:46:20 UTC 
Fixed, in f33 and rawhide.
Note You need to log in before you can comment on or make changes to this bug.