Details
-
Bug
-
Status: Open (View Workflow)
-
Minor
-
Resolution: Unresolved
-
10.4
-
None
Description
Observed locally a few times, when the tests were run on a rotating disk rather than in memory.
|
bb-10.4-release cc5b7fe1 (May 9th) |
binlog.binlog_innodb 'innodb,mix' w4 [ fail ]
|
Test ended at 2020-05-09 20:03:23
|
|
|
CURRENT_TEST: binlog.binlog_innodb
|
--- /data/bld/10.4.13-unstable-tests/mysql-test/suite/binlog/r/binlog_innodb.result 2020-05-09 15:05:13.000000000 +0300
|
+++ /data/bld/10.4.13-unstable-tests/mysql-test/suite/binlog/r/binlog_innodb.reject 2020-05-09 20:03:23.348862400 +0300
|
@@ -183,7 +183,7 @@
|
SELECT IF(@num_sync < 100*1.5, "OK",
|
CONCAT("ERROR: More than 1 fsync per commit (saw ", @num_sync/100, ")")) AS status;
|
status
|
-OK
|
+ERROR: More than 1 fsync per commit (saw 1.5800)
|
DROP TABLE t1;
|
SET GLOBAL innodb_flush_log_at_trx_commit=@old_flush;
|
End of tests
|
|
|
mysqltest: Result length mismatch
|
Possibly related to the previous tests. The full chain after the last server restart was this:
worker[4] > Restart [mysqld.1 - pid: 9900, winpid: 9900] - running with different options '--log-bin=master-bin --binlog-format=mixed --log-bin=master-bin' != '--log-bin=master-bin --log-bin=master-bin --binlog-format=mixed'
|
rpl.rpl_gtid_master_promote 'innodb,row' w4 [ pass ] 51363
|
rpl.rpl_heartbeat_2slaves 'stmt' w4 [ pass ] 8608
|
rpl.sequence 'row' w4 [ pass ] 1822
|
sys_vars.slave_parallel_threads_basic w4 [ pass ] 3
|
innodb.alter_not_null 'COPY,STRICT,innodb' w4 [ pass ] 47725
|
innodb.alter_not_null 'INPLACE,NON-STRICT,innodb' w4 [ pass ] 92473
|
binlog.binlog_stm_do_db 'innodb,stmt' w4 [ pass ] 17611
|
binlog.binlog_row_annotate 'row' w4 [ pass ] 469
|
binlog.binlog_innodb 'innodb,mix' w4 [ fail ]
|
but not reproducible on will even by re-running the whole set