On Sat, 12 Jan 2019 12:51:41 +0100, Andreas Beckmann wrote: > On 2019-01-12 12:42, Otto Kekäläinen wrote: > > Now with the mysql version fixed the mariadb version regressed. Does any of > > you spot what is the failure cause in > > https://ci.debian.net/data/autopkgtest/testing/amd64/libd/libdbd-mariadb-perl/1690599/log.gz > > ? > > not ok 16 - warning is correct > # Failed test 'warning is correct' > # at t/55utf8.t line 83. > # 'Incorrect string value: '\xC4\x80dam' for column > `testdb`.`dbd_mysql_t55utf8`.`ascii` at row 1' > # doesn't match '(?^:^(?:Incorrect string value: '\\xC4\\x80dam'|Data > truncated) for column 'ascii' at row 1$)' > > not ok 58 - warning is correct > # Failed test 'warning is correct' > # at t/55utf8.t line 83. > # 'Incorrect string value: '\xC4\x80dam' for column > `testdb`.`dbd_mysql_t55utf8`.`ascii` at row 1' > # doesn't match '(?^:^(?:Incorrect string value: '\\xC4\\x80dam'|Data > truncated) for column 'ascii' at row 1$)' > > The column name is now prefixed with `testdb`.`dbd_mysql_t55utf8`. and > quoted as `ascii` instead of 'ascii'
Thanks for noticing. I've filed this as a separate bug against libdbd-mariadb-perl in Debian and DBD-MariaDB upstream: https://bugs.debian.org/919071 https://github.com/gooddata/DBD-MariaDB/issues/121 Please continue the discussion there. (Note that adjusting the regexp for the expected message is no big deal but I'd rather have upstream take a look at this first.) Cheers, gregor -- .''`. 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: Eagles
signature.asc
Description: Digital Signature
