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

74 lines
2.6 KiB
Text
Raw Normal View History

Manual merge 5.0->5.1. Post-merge fixes.
2006-08-14 11:27:11 +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
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
--------------------------------------------------------------------
-- 1.1.2.
--------------------------------------------------------------------
WL#2789 "Instance Manager: test using mysql-test-run testing framework" Add Instance Manager tests.
2005-09-30 23:14:50 +02:00
START INSTANCE mysqld2;
Fix of test suite in scope of fixing BUG#18023: IM: instance can be started several times; monitor interval must be > 2sec
2006-06-19 12:13:34 +02:00
Success: the process has been started.
WL#2789 "Instance Manager: test using mysql-test-run testing framework" Add Instance Manager tests.
2005-09-30 23:14:50 +02:00
SHOW VARIABLES LIKE 'port';
Variable_name Value
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
port IM_MYSQLD2_PORT
--------------------------------------------------------------------
-- 1.1.3.
--------------------------------------------------------------------
WL#2789 "Instance Manager: test using mysql-test-run testing framework" Add Instance Manager tests.
2005-09-30 23:14:50 +02:00
STOP INSTANCE mysqld2;
Fix of test suite in scope of fixing BUG#18023: IM: instance can be started several times; monitor interval must be > 2sec
2006-06-19 12:13:34 +02:00
Success: the process has been stopped.
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
--------------------------------------------------------------------
-- 1.1.4.
--------------------------------------------------------------------
WL#2789 "Instance Manager: test using mysql-test-run testing framework" Add Instance Manager tests.
2005-09-30 23:14:50 +02:00
START INSTANCE mysqld3;
Fix Bug #22494 Instance Manager: Inconsistent error message wording Use better wording
2006-11-07 03:21:33 +01:00
ERROR HY000: Unknown instance name
WL#2789 "Instance Manager: test using mysql-test-run testing framework" Add Instance Manager tests.
2005-09-30 23:14:50 +02:00
START INSTANCE mysqld1;
ERROR HY000: The instance is already started
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
--------------------------------------------------------------------
-- 1.1.5.
--------------------------------------------------------------------
WL#2789 "Instance Manager: test using mysql-test-run testing framework" Add Instance Manager tests.
2005-09-30 23:14:50 +02:00
STOP INSTANCE mysqld3;
Fix Bug #22494 Instance Manager: Inconsistent error message wording Use better wording
2006-11-07 03:21:33 +01:00
ERROR HY000: Unknown instance name
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
--------------------------------------------------------------------
-- 1.1.6.
--------------------------------------------------------------------
WL#2789 "Instance Manager: test using mysql-test-run testing framework" Add Instance Manager tests.
2005-09-30 23:14:50 +02:00
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.
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
WL#2789 "Instance Manager: test using mysql-test-run testing framework" Add Instance Manager tests.
2005-09-30 23:14:50 +02:00
mysqld1 online
mysqld2 offline
Fix of test suite in scope of fixing BUG#18023: IM: instance can be started several times; monitor interval must be > 2sec
2006-06-19 12:13:34 +02:00
--------------------------------------------------------------------
-- 1.1.7.
--------------------------------------------------------------------
WL#2789 "Instance Manager: test using mysql-test-run testing framework" Add Instance Manager tests.
2005-09-30 23:14:50 +02:00
START INSTANCE mysqld2;
Fix of test suite in scope of fixing BUG#18023: IM: instance can be started several times; monitor interval must be > 2sec
2006-06-19 12:13:34 +02:00
Success: the process has been started.
WL#2789 "Instance Manager: test using mysql-test-run testing framework" Add Instance Manager tests.
2005-09-30 23:14:50 +02:00
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 killed.
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
--------------------------------------------------------------------
-- 1.1.8.
--------------------------------------------------------------------
a bunch of IM fixes from the GUI team
2006-02-10 00:15:55 +01:00
SHOW INSTANCE STATUS;
ERROR 42000: You have an error in your command syntax. Check the manual that corresponds to your MySQL Instance Manager version for the right syntax to use
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
--------------------------------------------------------------------
-- BUG#12813
--------------------------------------------------------------------
fix Bug#12813 "Instance Manager: START/STOP INSTANCE commands accept a list as argument"
2006-02-14 01:09:17 +01:00
START INSTANCE mysqld1,mysqld2,mysqld3;
ERROR 42000: You have an error in your command syntax. Check the manual that corresponds to your MySQL Instance Manager version for the right syntax to use
STOP INSTANCE mysqld1,mysqld2,mysqld3;
ERROR 42000: You have an error in your command syntax. Check the manual that corresponds to your MySQL Instance Manager version for the right syntax to use
Bug #12673: Instance Manager: allows to stop the instance many times The instance manager was not actually checking whether an instance was actually running before trying to stop it. Now it checks first.
2006-07-12 21:30:22 +02:00
STOP INSTANCE mysqld2;
ERROR HY000: Cannot stop instance. Perhaps the instance is not started, or was started manually, so IM cannot find the pidfile.
End of 5.0 tests
Reference in a new issue Copy permalink