mariadb/mysql-test/main/kill_processlist-6619.result

connect  con1,localhost,root,,;
SHOW PROCESSLIST;
Id	User	Host	db	Command	Time	State	Info	Progress
#	root	#	test	Sleep	#	#	NULL	0.000
#	root	#	test	Query	#	#	SHOW PROCESSLIST	0.000
SET DEBUG_SYNC='before_execute_sql_command SIGNAL ready WAIT_FOR go';
SHOW PROCESSLIST;
connection default;
SET DEBUG_SYNC='now WAIT_FOR ready';
KILL QUERY con_id;
SET DEBUG_SYNC='now SIGNAL go';
connection con1;
ERROR 70100: Query execution was interrupted
SET DEBUG_SYNC='reset';
SHOW PROCESSLIST;
Id	User	Host	db	Command	Time	State	Info	Progress
#	root	#	test	Sleep	#	#	NULL	0.000
#	root	#	test	Query	#	#	SHOW PROCESSLIST	0.000
MDEV-6619 SHOW PROCESSLIST returns empty result set after KILL QUERY don't send an OK packet if the SHOW PROCESSLIST was killed 2014-09-12 08:41:35 +02:00			`connect con1,localhost,root,,;`
			`SHOW PROCESSLIST;`
			`Id User Host db Command Time State Info Progress`
			`# root # test Sleep # # NULL 0.000`
			`# root # test Query # # SHOW PROCESSLIST 0.000`
MDEV-7352: main.kill_processlist-6619 fails sporadically in buildbot After fix of MDEV-6728, the KILL signal is reset at the start of query execution. This means that in this test case, we need to wait for the to-be-killed query to have started; otherwise the kill signal can be lost, causing the test case to fail. 2015-01-23 13:56:46 +01:00			`SET DEBUG_SYNC='before_execute_sql_command SIGNAL ready WAIT_FOR go';`
MDEV-6728 KILL QUERY executed on an idle connection can interrupt the next query reset KILL_QUERY when a new query execution is just about to be started 2015-01-19 14:07:41 +01:00			`SHOW PROCESSLIST;`
MDEV-6619 SHOW PROCESSLIST returns empty result set after KILL QUERY don't send an OK packet if the SHOW PROCESSLIST was killed 2014-09-12 08:41:35 +02:00			`connection default;`
MDEV-7352: main.kill_processlist-6619 fails sporadically in buildbot After fix of MDEV-6728, the KILL signal is reset at the start of query execution. This means that in this test case, we need to wait for the to-be-killed query to have started; otherwise the kill signal can be lost, causing the test case to fail. 2015-01-23 13:56:46 +01:00			`SET DEBUG_SYNC='now WAIT_FOR ready';`
MDEV-6619 SHOW PROCESSLIST returns empty result set after KILL QUERY don't send an OK packet if the SHOW PROCESSLIST was killed 2014-09-12 08:41:35 +02:00			`KILL QUERY con_id;`
MDEV-6728 KILL QUERY executed on an idle connection can interrupt the next query reset KILL_QUERY when a new query execution is just about to be started 2015-01-19 14:07:41 +01:00			`SET DEBUG_SYNC='now SIGNAL go';`
MDEV-6619 SHOW PROCESSLIST returns empty result set after KILL QUERY don't send an OK packet if the SHOW PROCESSLIST was killed 2014-09-12 08:41:35 +02:00			`connection con1;`
			`ERROR 70100: Query execution was interrupted`
MDEV-7352: main.kill_processlist-6619 fails sporadically in buildbot After fix of MDEV-6728, the KILL signal is reset at the start of query execution. This means that in this test case, we need to wait for the to-be-killed query to have started; otherwise the kill signal can be lost, causing the test case to fail. 2015-01-23 13:56:46 +01:00			`SET DEBUG_SYNC='reset';`
MDEV-6619 SHOW PROCESSLIST returns empty result set after KILL QUERY don't send an OK packet if the SHOW PROCESSLIST was killed 2014-09-12 08:41:35 +02:00			`SHOW PROCESSLIST;`
			`Id User Host db Command Time State Info Progress`
			`# root # test Sleep # # NULL 0.000`
			`# root # test Query # # SHOW PROCESSLIST 0.000`