Analysis of working_dml/misc/bug3283.sql : This query is reporting failure - because the reference log is incorrect, the reference log in working_dml/misc/bug3283.sql.ref.log is showing

ERROR 1305 (42000) at line 2: FUNCTION dml.caldroppartitions does not exist

I looked reference log when we ran the same test against InfiniDB - This is how it is

caldroppartitions('lineitem', '4.1.1')

No partitions are dropped

caldisablepartitions('lineitem', '4.1.1')

No partitions are disabled

hill bug3283.sql.ref.log log file needs to be fixed with the above shown text lines

Analysis of Ref failed - working_dml/misc/bug3326b.sql

more bug3326b.sql.diff

0a1

> ERROR 1969 (70100) at line 5: Query execution was interrupted (max_statement_time exceeded)

3,34d3

< count(*)

< 99996

< count(*)

bug3326b.sql.ref.log ( log of same query ran against reference database - MariaDB Server ISAM table)

ERROR 1969 (70100) at line 5: Query execution was interrupted (max_statement_time exceeded)

count(*)

99996

This is due to having set max_statement_time in my.cnf of MariaDB Server - according to MariaDB Server documentation https://mariadb.com/kb/en/mariadb/aborting-statements/ if we set the max_statement_time to 0, then no such limit will be applied, and longer running query will not be interrupted.

ref log updated for bug3283

Looks like bug3283.sql failure is cleared up

Analysis of current remaining failures

(1) Ref failed - working_dml/misc/bug3326b.sql : Need to set max_statement_time to 0 as commented earlier. - Should run this manually on reference database to further find root cause
(2) Ref failed - working_dml/misc/multiupdate_001.sql Reference database is complaining about duplicate column- this should not happen
(3) Ref failed - working_dml/misc/multiupdate_002.sql Reference database is complaining about duplicate column- this should not happen

(4) Following are giving same error message in columnstore log "ERROR 1049 (42000): Unknown database 'dml'" - This implies some how the database is getting dropped during the run . Need to look at this on actual regression machine

Compare failed - working_dml/misc/bug2741.sql
Compare failed - working_dml/misc/bug3040c.sql
Compare failed - working_dml/misc/bug3129.sql
Compare failed - working_dml/misc/bug3279.sql
Compare failed - working_dml/misc/bug3997.sql
Compare failed - working_dml/misc/bug5096.sql
Compare failed - working_dml/misc/subupd003.sql
Compare failed - working_dml/misc/vtabledmlcol2col.sql
Compare failed - working_dml/qa_sub/mts_insert_select.sql

updated ref logs and now passing test

Fixed by using correct reference log for the tests - instead of going to reference DB, get the correct expected result from InfiniDB run and use it as reference log