Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.1(EOL)
Description
Cross-reference shows a couple of failures on 10.0, but mainly it's 10.1. Maybe it has already been fixed in 10.0 and 10.1 is just waiting for a merge?
rpl.rpl_mdev6386 'row,xtradb' w2 [ fail ]
|
Test ended at 2014-12-17 08:24:08
|
|
|
CURRENT_TEST: rpl.rpl_mdev6386
|
--- /usr/share/mysql/mysql-test/suite/rpl/r/rpl_mdev6386.result 2014-12-16 12:55:44.000000000 +0100
|
+++ /dev/shm/var/2/log/rpl_mdev6386.reject 2014-12-17 08:24:03.631177126 +0100
|
@@ -44,11 +44,6 @@
|
Contents on slave after:
|
SELECT * FROM t1 ORDER BY a;
|
a b
|
-1 1
|
-2 1
|
-3 1
|
-4 1
|
-5 1
|
DROP TABLE t1;
|
include/stop_slave.inc
|
SET GLOBAL slave_parallel_threads= @old_parallel;
|
|
|
mysqltest: Result length mismatch
|
After a quick look at the test, I don't see anything wrong with it, so my suspicion is it can be a real code problem (at best, sync_with_master not working correctly with parallel replication; at worst, parallel replication itself not working right on resuming after a previous error). It's just my wild guesses though.
Attachments
Issue Links
- relates to
-
MDEV-7172 Fix buildbot failures in 10.1 tree
-
- Closed
-