mirror/mariadb
1
0
Fork 0
mirror of https://github.com/MariaDB/server.git synced 2025-01-20 22:12:30 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
mariadb/mysql-test/r/im_daemon_life_cycle.result

27 lines
802 B
Text
Raw Normal View History

Fix for BUG#20716: SHOW INSTANCES statement causes races in IM tests. Fix for the bug in mysql-test-run.pl which prevents other tests succeed after IM-test failure. The idea of the fix of BUG#20716 is to: 1. Check each SHOW INSTANCES statement, add necessary "sleep" instruction before; 2. Move all environment checkings into the one file and include it everywhere.
2006-07-20 11:24:12 +02:00
SHOW VARIABLES LIKE 'server_id';
Variable_name Value
server_id 1
WL#2789 "Instance Manager: test using mysql-test-run testing framework" Add Instance Manager tests.
2005-09-30 23:14:50 +02:00
SHOW INSTANCES;
This is an implementation of two WL items: - WL#3158: IM: Instance configuration extensions; - WL#3159: IM: --bootstrap and --start-default-instance modes The following new statements have been added: - CREATE INSTANCE; - DROP INSTANCE; The behaviour of the following statements have been changed: - SET; - UNSET; - FLUSH INSTANCES; - SHOW INSTANCES; - SHOW INSTANCE OPTIONS;
2006-05-18 16:57:50 +02:00
instance_name state
Fixed a LOT of compiler warnings Added missing DBUG_RETURN statements (in mysqldump.c) Added missing enums Fixed a lot of wrong DBUG_PRINT() statements, some of which could cause crashes Removed usage of %lld and %p in printf strings as these are not portable or produces different results on different systems.
2006-11-27 00:47:38 +01:00
mysqld1 XXXXX
WL#2789 "Instance Manager: test using mysql-test-run testing framework" Add Instance Manager tests.
2005-09-30 23:14:50 +02:00
mysqld2 offline
Killing the process...
Fix for BUG##24415: Instance manager test im_daemon_life_cycle fails randomly. The problem was that the test case used command line tool (mysql) without specifying connect_timeout argument. In some cases, this lead to hanging of the test case. The fix is to specify --connect_timeout=1 when starting mysql. Also, the patch contains polishing and various cleanups to simplify analyzing of the problems further. The patch affects only test suite, no server codebase has been touched.
2006-11-23 20:55:36 +01:00
Waiting...
WL#2789 "Instance Manager: test using mysql-test-run testing framework" Add Instance Manager tests.
2005-09-30 23:14:50 +02:00
Success: the process was restarted.
Patch for BUG#15934: im_daemon_life_cycle fails sporadically. The problem was a race condition in a test case. The fix eliminates the race condition by explicit wait on UNIX socket to start accepting connections. The patch affects only test suite (i.e. does not touch server codebase).
2006-10-03 16:42:59 +02:00
Success: server is ready to accept connection on socket.
Fix for BUG#12751: Instance Manager: client hangs after start instance; kill mysqlmanager; show ... The problem was that Instance Manager didn't close client sockets (sockets for client connections) on execing mysqld instance. So, mysqld-instance inherits these descriptors. The fix is to set close-on-exec flag for each client socket.
2006-09-01 16:20:33 +02:00
--------------------------------------------------------------------
-- Test for BUG#12751
--------------------------------------------------------------------
START INSTANCE mysqld2;
Success: the process has been started.
Killing the process...
Fix for BUG##24415: Instance manager test im_daemon_life_cycle fails randomly. The problem was that the test case used command line tool (mysql) without specifying connect_timeout argument. In some cases, this lead to hanging of the test case. The fix is to specify --connect_timeout=1 when starting mysql. Also, the patch contains polishing and various cleanups to simplify analyzing of the problems further. The patch affects only test suite, no server codebase has been touched.
2006-11-23 20:55:36 +01:00
Waiting...
Fix for BUG#12751: Instance Manager: client hangs after start instance; kill mysqlmanager; show ... The problem was that Instance Manager didn't close client sockets (sockets for client connections) on execing mysqld instance. So, mysqld-instance inherits these descriptors. The fix is to set close-on-exec flag for each client socket.
2006-09-01 16:20:33 +02:00
Success: the process was restarted.
Wait for IM to start accepting connections after restart (part 2).
2006-11-02 19:43:52 +01:00
Success: server is ready to accept connection on socket.
Fix for BUG#12751: Instance Manager: client hangs after start instance; kill mysqlmanager; show ... The problem was that Instance Manager didn't close client sockets (sockets for client connections) on execing mysqld instance. So, mysqld-instance inherits these descriptors. The fix is to set close-on-exec flag for each client socket.
2006-09-01 16:20:33 +02:00
SHOW INSTANCE STATUS mysqld1;
5.0-rt -> 5.1-rt after-merge fixes.
2006-09-28 13:40:23 +02:00
instance_name state version_number version mysqld_compatible
Merge alik.opbmk:/mnt/raid/alik/MySQL/devel/5.0-rt-build into alik.opbmk:/mnt/raid/alik/MySQL/devel/5.1-rt-build
2007-02-23 19:55:14 +01:00
mysqld1 STATE VERSION_NUMBER VERSION no
Fix for BUG#12751: Instance Manager: client hangs after start instance; kill mysqlmanager; show ... The problem was that Instance Manager didn't close client sockets (sockets for client connections) on execing mysqld instance. So, mysqld-instance inherits these descriptors. The fix is to set close-on-exec flag for each client socket.
2006-09-01 16:20:33 +02:00
STOP INSTANCE mysqld2;
Success: the process has been stopped.
Reference in a new issue Copy permalink