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 1987776 - openqa: FTBFS in Fedora rawhide/f35
Summary: openqa: FTBFS in Fedora rawhide/f35
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: openqa
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Williamson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F35FTBFS
TreeView+ depends on / blocked
 
Reported: 2021-07-29 16:16 UTC by Fedora Release Engineering
Modified: 2021-07-29 22:33 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-07-29 22:33:54 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
build.log (deleted)
2021-07-29 16:17 UTC, Fedora Release Engineering 		no flags Details
root.log (deleted)
2021-07-29 16:17 UTC, Fedora Release Engineering 		no flags Details
state.log (deleted)
2021-07-29 16:17 UTC, Fedora Release Engineering 		no flags Details
View All

Description Fedora Release Engineering 2021-07-29 16:16:58 UTC 
openqa failed to build from source in Fedora rawhide/f35

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


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_35_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 36,
openqa will be retired, if it still fails to build.

For more details on the FTBFS policy, please visit:
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
Comment 1 Fedora Release Engineering 2021-07-29 16:17:02 UTC 
Created attachment 1808235 [details]
build.log

file build.log too big, will only attach last 32768 bytes
Comment 2 Fedora Release Engineering 2021-07-29 16:17:06 UTC 
Created attachment 1808236 [details]
root.log

file root.log too big, will only attach last 32768 bytes
Comment 3 Fedora Release Engineering 2021-07-29 16:17:08 UTC 
Created attachment 1808237 [details]
state.log
Comment 4 Adam Williamson 2021-07-29 16:45:05 UTC 
This is awkward. It's failing on a deprecation warning in a test that asserts no warnings:

./t/25-cache-client.t ....................................... ok
"sqlite_unicode" attribute will be deprecated. Use "sqlite_string_mode" instead. at /usr/lib64/perl5/vendor_perl/DBI.pm line 734.
"sqlite_unicode" attribute will be deprecated. Use "sqlite_string_mode" instead. at /usr/lib64/perl5/vendor_perl/DBI.pm line 734.
"sqlite_unicode" attribute will be deprecated. Use "sqlite_string_mode" instead. at /usr/lib64/perl5/vendor_perl/DBI.pm line 734.
"sqlite_unicode" attribute will be deprecated. Use "sqlite_string_mode" instead. at /usr/lib64/perl5/vendor_perl/DBI.pm line 734.
"sqlite_unicode" attribute will be deprecated. Use "sqlite_string_mode" instead. at /usr/lib64/perl5/vendor_perl/DBI.pm line 734.
"sqlite_unicode" attribute will be deprecated. Use "sqlite_string_mode" instead. at /usr/lib64/perl5/vendor_perl/DBI.pm line 734.
"sqlite_unicode" attribute will be deprecated. Use "sqlite_string_mode" instead. at /usr/lib64/perl5/vendor_perl/DBI.pm line 734.
"sqlite_unicode" attribute will be deprecated. Use "sqlite_string_mode" instead. at /usr/lib64/perl5/vendor_perl/DBI.pm line 734.
"sqlite_unicode" attribute will be deprecated. Use "sqlite_string_mode" instead. at /usr/lib64/perl5/vendor_perl/DBI.pm line 734.
"sqlite_unicode" attribute will be deprecated. Use "sqlite_string_mode" instead. at /usr/lib64/perl5/vendor_perl/DBI.pm line 734.
"sqlite_unicode" attribute will be deprecated. Use "sqlite_string_mode" instead. at /usr/lib64/perl5/vendor_perl/DBI.pm line 734.
"sqlite_unicode" attribute will be deprecated. Use "sqlite_string_mode" instead. at /usr/lib64/perl5/vendor_perl/DBI.pm line 734.
"sqlite_unicode" attribute will be deprecated. Use "sqlite_string_mode" instead. at /usr/lib64/perl5/vendor_perl/DBI.pm line 734.
"sqlite_unicode" attribute will be deprecated. Use "sqlite_string_mode" instead. at /usr/lib64/perl5/vendor_perl/DBI.pm line 734.
"sqlite_unicode" attribute will be deprecated. Use "sqlite_string_mode" instead. at /usr/lib64/perl5/vendor_perl/DBI.pm line 734.
"sqlite_unicode" attribute will be deprecated. Use "sqlite_string_mode" instead. at /usr/lib64/perl5/vendor_perl/DBI.pm line 734.
"sqlite_unicode" attribute will be deprecated. Use "sqlite_string_mode" instead. at /usr/lib64/perl5/vendor_perl/DBI.pm line 734.
#   Failed test 'no (unexpected) warnings (via done_testing)'

but I don't know where that's coming from. "sqlite_unicode" does not appear in the openQA, os-autoinst, or perl-DBI code anywhere that I can see. I've no idea where it's coming in from. Line 734 of DBI.pm is in this loop:

    733             while ( my ($a, $v) = each %$apply) {
    734                 eval { $dbh->{$a} = $v }; # assign in void context to avoid re-FETCH
    735                 warn $@ if $@;
    736             }

which is gonna take some unpicking.
Comment 5 Adam Williamson 2021-07-29 18:09:16 UTC 
https://github.com/DBD-SQLite/DBD-SQLite/issues/87 is the best I can do for now. I'll see if I can patch the test to just 'expect' these warnings so we can get a build done.
Comment 6 Adam Williamson 2021-07-29 21:52:42 UTC 
OK, so upstream removed the deprecation warning, I backported that to Rawhide and am running a new openQA build, that will hopefully go through.
Comment 7 Adam Williamson 2021-07-29 22:33:54 UTC 
Fixed: https://koji.fedoraproject.org/koji/taskinfo?taskID=72935441
Note You need to log in before you can comment on or make changes to this bug.