Bug 1424103

Summary: polyml: FTBFS in rawhide
Product: [Fedora] Fedora Reporter: Fedora Release Engineering <releng>
Component: polymlAssignee: Jerry James <loganjerry>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: dmoerner, loganjerry
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-02-28 04:43:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1423041    
Attachments:
Description Flags
build.log
none
root.log
none
state.log none

Description Fedora Release Engineering 2017-02-17 15:55:03 UTC 
Your package polyml failed to build from source in current rawhide.

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

For details on mass rebuild see https://fedoraproject.org/wiki/Fedora_26_Mass_Rebuild
Comment 1 Fedora Release Engineering 2017-02-17 15:55:08 UTC 
Created attachment 1253607 [details]
build.log
Comment 2 Fedora Release Engineering 2017-02-17 15:55:11 UTC 
Created attachment 1253608 [details]
root.log
Comment 3 Fedora Release Engineering 2017-02-17 15:55:14 UTC 
Created attachment 1253609 [details]
state.log
Comment 4 Daniel Moerner 2017-02-28 02:41:55 UTC 
This bug was first mentioned as a comment here: https://bugzilla.gnome.org/show_bug.cgi?id=650371#c42

Now that there are ppc64 test instances I hope to try to work on this as well, although it doesn't look easy.
Comment 5 Jerry James 2017-02-28 04:20:27 UTC 
(In reply to Daniel Moerner from comment #4)
> This bug was first mentioned as a comment here:
> https://bugzilla.gnome.org/show_bug.cgi?id=650371#c42

Are you sure you pasted the right URL in?  That one doesn't have any obvious connection to polyml.

> Now that there are ppc64 test instances I hope to try to work on this as
> well, although it doesn't look easy.

I just did a test build on the new ppc64 test instance to see how hard this will be to debug ... and the build succeeded.  I'm going to try kicking of a full build and see what happens.  This failure may have been due to a problem in some other component that has since been fixed.  (Or worse, it may be an intermittent failure.  I hope it isn't that.)
Comment 6 Jerry James 2017-02-28 04:43:33 UTC 
The full build succeeded.  I'm going to hope that means that the problem, whatever it was, has disappeared.  If it reappears we can reopen this bug.