Commit c217fd6a authored by Vladislav Vaintroub's avatar Vladislav Vaintroub

Fix test suite:

on Windows, kill <connection> can and almost always will return client error 2013 ("Lost connection...") on the killed connection,
On the server side, if connection is "sleeping" KILL will close the socket, thus  socket error on client is expected.
parent 2bed41d4
...@@ -96,7 +96,8 @@ drop table t2; ...@@ -96,7 +96,8 @@ drop table t2;
connection master; connection master;
# The get_lock function causes warning for unsafe statement. # The get_lock function causes warning for unsafe statement.
--disable_warnings --disable_warnings
--error ER_QUERY_INTERRUPTED,ER_CONNECTION_KILLED # 2013 = CR_SERVER_LOST
--error ER_QUERY_INTERRUPTED,ER_CONNECTION_KILLED,2013
reap; reap;
--enable_warnings --enable_warnings
connection slave; connection slave;
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment