[MDEV-10620] multi_source.gtid fails sporadically in buildbot Created: 2016-08-21  Updated: 2017-02-24  Resolved: 2017-02-24

Status: Closed
Project: MariaDB Server
Component/s: Tests
Affects Version/s: 10.0, 10.1
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Elena Stepanova
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-7069 Fix buildbot failures in main server ... Stalled
Sprint: 5.5.55, 10.0.30

 Description   

The test produces different failures. Examples:

http://buildbot.askmonty.org/buildbot/builders/p8-trusty-bintar/builds/25/steps/test/logs/stdio

multi_source.gtid 'xtradb'               w3 [ fail ]
        Test ended at 2016-07-01 03:01:12
 
CURRENT_TEST: multi_source.gtid
--- /var/lib/buildbot/maria-slave/p8-trusty-bintar/build/mysql-test/suite/multi_source/gtid.result	2016-06-30 18:38:40.329974188 -0400
+++ /var/lib/buildbot/maria-slave/p8-trusty-bintar/build/mysql-test/suite/multi_source/gtid.reject	2016-07-01 03:01:11.994300928 -0400
@@ -77,6 +77,11 @@
 connection slave1;
 CHANGE MASTER TO master_port=MYPORT_4, master_host='127.0.0.1', master_user='root', master_use_gtid=current_pos;
 START SLAVE;
+Timeout in wait_condition.inc for SELECT (SELECT COUNT(*) FROM t1)=3 AND (SELECT COUNT(*) FROM t2)=4 AND (SELECT COUNT(*) FROM t3)=7
+Id	User	Host	db	Command	Time	State	Info	Progress
+4	root	localhost:35841	test	Query	0	init	show full processlist	0.000
+10	system user		NULL	Connect	41	Waiting for master to send event	NULL	0.000
+11	system user		NULL	Connect	40	Unlocking tables	NULL	0.000
 SELECT * FROM t1 ORDER BY a;
 a	b
 1	initial
@@ -87,16 +92,13 @@
 1	initial
 2	switch1
 3	switch 2
-4	switch 3
 SELECT * FROM t3 ORDER BY a;
 a	b
 101	initial 1
 102	switch1 a
-103	switch 2 a
 201	initial 2
 202	switch1 b
 203	switch 2 b
-204	switch 3 b
 connection master1;
 DROP TABLE t1;
 SET SQL_LOG_BIN=0;

# logs not available
# 0.0	1f761c5615c7414d1ccd88ceb7027202	p8-trusty-bintar	2016-06-22 04:38:18	1082	nm	Normal run, no --ps-protocol	multi_source.gtid	xtradb

multi_source.gtid 'xtradb'               w4 [ fail ]
        Test ended at 2016-06-21 21:51:20
 
CURRENT_TEST: multi_source.gtid
--- /var/lib/buildbot/maria-slave/p8-trusty-bintar/build/mysql-test/suite/multi_source/gtid.result	2016-06-20 22:05:49.582216586 -0400
+++ /var/lib/buildbot/maria-slave/p8-trusty-bintar/build/mysql-test/suite/multi_source/gtid.reject	2016-06-21 21:51:19.400341815 -0400
@@ -83,6 +83,11 @@
 DROP TABLE t2;
 DROP TABLE t3;
 SET GLOBAL gtid_domain_id=0;
+Timeout in wait_condition.inc for SELECT COUNT(*)=0 FROM information_schema.tables WHERE table_name IN ("t1", "t2", "t3") AND table_schema = "test"
+Id	User	Host	db	Command	Time	State	Info	Progress
+4	root	localhost:46772	test	Query	0	init	show full processlist	0.000
+10	system user		NULL	Connect	41	Waiting for master to send event	NULL	0.000
+11	system user		test	Connect	37	closing tables	DROP TABLE IF EXISTS `t3` /* generated by server */	0.000
 STOP ALL SLAVES;
 Warnings:
 Note	1938	SLAVE '' stopped
 
mysqltest: Result length mismatch



 Comments   
Comment by Elena Stepanova [ 2017-02-24 ]

In recent history the timeouts were observed on p8 builders.
After they were switched to using --mem, the average execution time for the test reduced 10 times, and timeouts aren't happening anymore.
Closing for now.

Generated at Thu Feb 08 07:43:38 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.