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' Andreas
