On Mon, 25 Feb 2019 14:15:29 +0200, Otto Kekäläinen wrote: (removing the bug from cc, which is archived, and adding debian-perl@l.d.o and upstream) > Now ci tests for libdbd-mysql-perl are failing again: > https://ci.debian.net/packages/libd/libdbd-mysql-perl/testing/amd64/ Hooray :) > It seems it cannot connect to the database, but the test output is too > verbose for me do grasp: > https://ci.debian.net/data/autopkgtest/testing/amd64/libd/libdbd-mysql-perl/1999434/log.gz No, the failrure is, for both mysql and mariadb (output from my local autopkgtest run in unstable): t/rt118977-zerofill.t ................... 1..8 ok 1 ok 2 ok 3 ok 4 ok 5 ok 6 ok 7 not ok 8 # Failed test at t/rt118977-zerofill.t line 22. # got: '1' # expected: '00001' # Looks like you failed 1 test of 8. Dubious, test returned 1 (wstat 256, 0x100) Failed 1/8 subtests … Test Summary Report ------------------- t/rt118977-zerofill.t (Wstat: 256 Tests: 8 Failed: 1) Failed test: 8 Non-zero exit status: 1 Files=72, Tests=2310, 33 wallclock secs ( 0.44 usr 0.11 sys + 6.47 cusr 0.90 csys = 7.92 CPU) Result: FAIL … autopkgtest [16:41:09]: test pkg-perl-autopkgtest-build-deps-mariadb: - - - - - - - - - - results - - - - - - - - - - pkg-perl-autopkgtest-build-deps-mariadb FAIL non-zero exit status 1 t/rt118977-zerofill.t ................... 1..8 ok 1 ok 2 ok 3 ok 4 ok 5 ok 6 ok 7 not ok 8 # Failed test at t/rt118977-zerofill.t line 22. # got: '1' # expected: '00001' # Looks like you failed 1 test of 8. Dubious, test returned 1 (wstat 256, 0x100) Failed 1/8 subtests … Test Summary Report ------------------- t/rt118977-zerofill.t (Wstat: 256 Tests: 8 Failed: 1) Failed test: 8 Non-zero exit status: 1 Files=72, Tests=2318, 37 wallclock secs ( 0.48 usr 0.09 sys + 6.39 cusr 0.96 csys = 7.92 CPU) Result: FAIL … autopkgtest [16:43:36]: test pkg-perl-autopkgtest-build-deps-mysql: - - - - - - - - - - results - - - - - - - - - - pkg-perl-autopkgtest-build-deps-mysql FAIL non-zero exit status 1 which is exactly the same as in #917303 [0] which puzzles me, as the bug was fixed in 4.050-1 and we've seen successful tests since then. This was a pure autopkgtest without a rebuild or anything. If I rebuild the package without any changes, I get the exact same test error. So we again have a FTBFS due to a change in mariadb. > I just uploaded MariaDB 10.3.13 with latest version of MariaDB > Connector C and due to I had to switch using GnuTLS in MariaDB > Connector C. Some of these changes triggered the error. Hm. FWIW: Rebuilding without the build dependency on libssl-dev lead to the same failure. Looks like there was a change in the MariaDB connector regarding the zerofill stuff between 10.3.12 and 10.3.13? Cheers, gregor [0] and https://github.com/perl5-dbi/DBD-mysql/issues/275 -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- NP: Kings of Convenience: Parallel Lines
Attachment:
signature.asc
Description: Digital Signature