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 1865165

Summary: openqa: FTBFS in Fedora rawhide/f33
Product: [Fedora] Fedora Reporter: Fedora Release Engineering <releng>
Component: openqaAssignee: Adam Williamson <awilliam>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: awilliam
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: 2020-08-04 22:05:55 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: 1803234    
Attachments:
Description Flags
build.log
none
root.log
none
state.log none

Description Fedora Release Engineering 2020-08-03 20:37:18 UTC
openqa failed to build from source in Fedora rawhide/f33

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


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_33_Mass_Rebuild
Please fix openqa 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,
openqa will be orphaned. Before branching of Fedora 34,
openqa 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 20:37:19 UTC
Created attachment 1708687 [details]
build.log

Comment 2 Fedora Release Engineering 2020-08-03 20:37:21 UTC
Created attachment 1708688 [details]
root.log

file root.log too big, will only attach last 32768 bytes

Comment 3 Fedora Release Engineering 2020-08-03 20:37:22 UTC
Created attachment 1708689 [details]
state.log

Comment 4 Adam Williamson 2020-08-04 15:44:59 UTC
So this was initially due to opencv needing a rebuild. However, it still doesn't build, and it seems it hasn't since Mojolicious 8.50 landed, because a warning was added to Mojo which gets triggered a lot during openQA tests with our nerfed network environment, and openQA tests are set to fail if any unexpected warnings appear :( e.g.:

Unhandled rejected promise: Connection refused at /usr/share/perl5/vendor_perl/Mojo/Reactor/Poll.pm line 131.
Unhandled rejected promise: Connection refused at /usr/share/perl5/vendor_perl/Mojo/Reactor/Poll.pm line 131.
Unhandled rejected promise: Connection refused at /usr/share/perl5/vendor_perl/Mojo/Reactor/Poll.pm line 131.
Unhandled rejected promise: Connection refused at /usr/share/perl5/vendor_perl/Mojo/Reactor/Poll.pm line 131.
Unhandled rejected promise: Connection refused at /usr/share/perl5/vendor_perl/Mojo/Reactor/Poll.pm line 131.
Unhandled rejected promise: Connection refused at /usr/share/perl5/vendor_perl/Mojo/Reactor/Poll.pm line 131.
Unhandled rejected promise: Connection refused at /usr/share/perl5/vendor_perl/Mojo/Reactor/Poll.pm line 131.
Unhandled rejected promise: Connection refused at /usr/share/perl5/vendor_perl/Mojo/Reactor/Poll.pm line 131.
Unhandled rejected promise: Connection refused at /usr/share/perl5/vendor_perl/Mojo/Reactor/Poll.pm line 131.
Unhandled rejected promise: Connection refused at /usr/share/perl5/vendor_perl/Mojo/Reactor/Poll.pm line 131.
#   Failed test 'no (unexpected) warnings (via done_testing)'
#   at ./t/api/02-iso-download.t line 210.
# Looks like you failed 1 test of 143.
./t/api/02-iso-download.t ........................ 
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/143 subtests 

to 'fix' this we either need to whitelist the warning somehow, or suppress Mojolicious from emitting it, but there doesn't seem to be a convenient way to do either. I'm poking relevant folks for ideas about the best way to deal with this.

Comment 5 Adam Williamson 2020-08-04 22:05:38 UTC
OK, I bumped to a slightly newer snapshot and it built now:

https://koji.fedoraproject.org/koji/buildinfo?buildID=1583403