Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.2(EOL)
-
None
-
10.2.4-2
Description
rpl.rpl_gtid_stop_start 'innodb,row' w1 [ fail ]
|
Test ended at 2016-12-21 04:28:24
|
|
CURRENT_TEST: rpl.rpl_gtid_stop_start
|
--- /usr/local/mariadb-10.2.3-linux-x86_64/mysql-test/suite/rpl/r/rpl_gtid_stop_start.result 2016-12-20 21:52:34.000000000 +0100
|
+++ /usr/local/mariadb-10.2.3-linux-x86_64/mysql-test/suite/rpl/r/rpl_gtid_stop_start.reject 2016-12-21 04:28:24.000000000 +0100
|
@@ -108,6 +108,10 @@
|
5
|
6
|
7
|
+Warnings:
|
+Error 145 Table './test/t1' is marked as crashed and should be repaired
|
+Error 1194 Table 't1' is marked as crashed and should be repaired
|
+Error 1034 1 client is using or hasn't closed the table properly
|
*** MDEV-4486: Allow to start old-style replication even if mysql.gtid_slave_pos is unavailable
|
connection server_2;
|
include/stop_slave.inc
|
|
mysqltest: Result length mismatch
|
Attachments
Issue Links
- relates to
-
MDEV-7069 Fix buildbot failures in main server trees
- Stalled
-
MDEV-12731 rpl.rpl_gtid_stop_start fails with Valgrind in buildbot and outside
- Closed