mirror/mariadb
1
0
Fork 0
mirror of https://github.com/MariaDB/server.git synced 2025-01-27 09:14:17 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
mariadb/mysql-test/main/named_pipe.test

31 lines
984 B
Text
Raw Normal View History

Add test for named pipes on windows Improve test for shm on windows mysql-test/include/windows.inc: improve "skip message" and don't require a result file mysql-test/r/shm.result: Update result after adding more tests mysql-test/t/shm-master.opt: Add $MTR_BUILD_THREAD to get a unique shared memory base name mysql-test/t/shm.test: Run a bunch of more test to check shm mysql-test/r/named_pipe.result: New BitKeeper file ``mysql-test/r/named_pipe.result'' mysql-test/t/named_pipe-master.opt: New BitKeeper file ``mysql-test/t/named_pipe-master.opt'' mysql-test/t/named_pipe.test: New BitKeeper file ``mysql-test/t/named_pipe.test''
2007-09-24 12:42:44 +02:00
# We currently only have named pipe support on windows, so
# in order to optimize things we skip this test on all
# other platforms
--source include/windows.inc
MWL#192: Non-blocking client API for libmysqlclient. All client functions that can block on I/O have alternate _start() and _cont() versions that do not block but return control back to the application, which can then issue I/O wait in its own fashion and later call back into the library to continue the operation. Works behind the scenes by spawning a co-routine/fiber to run the blocking operation and suspend it while waiting for I/O. This co-routine/fiber use is invisible to applications. For i368/x86_64 on GCC, uses very fast assembler co-routine support. On Windows uses native Win32 Fibers. Falls back to POSIX ucontext on other platforms. Assembler routines for more platforms are relatively easy to add by extending mysys/my_context.c, eg. similar to the Lua lcoco library. For testing, mysqltest and mysql_client_test are extended with the option --non-blocking-api. This causes the programs to use the non-blocking API for database access. mysql-test-run.pl has a similar option --non-blocking-api that uses this, as well as additional testcases. An example program tests/async_queries.c is included that uses the new non-blocking API with libevent to show how, in a single-threaded program, to issue many queries in parallel against a database. client/async_example.c: Fix const warning ****** Fix bug with wrong timeout value for poll(). include/Makefile.am: Fix missing include for `make dist` include/mysql.h: Add prototypes for all non-blocking API calls. include/mysql.h.pp: Add prototypes for all non-blocking API calls. mysys/my_context.c: Fix type warning for makecontext() function pointer argument. sql-common/mysql_async.c: Fix crashes in the non-blocking API for functions that can take MYSQL argument that is NULL. tests/Makefile.am: Add header file to `make dist` tests/mysql_client_test.c: Replace blocking calls with wrappers around the non-blocking calls, used in mysql_client_test to test the new non-blocking API. tests/nonblock-wrappers.h: Replace blocking calls with wrappers around the non-blocking calls, used in mysql_client_test to test the new non-blocking API.
2011-09-20 12:49:25 +02:00
# Named pipe does not support the non-blocking API.
--disable_non_blocking_api
Add test for named pipes on windows Improve test for shm on windows mysql-test/include/windows.inc: improve "skip message" and don't require a result file mysql-test/r/shm.result: Update result after adding more tests mysql-test/t/shm-master.opt: Add $MTR_BUILD_THREAD to get a unique shared memory base name mysql-test/t/shm.test: Run a bunch of more test to check shm mysql-test/r/named_pipe.result: New BitKeeper file ``mysql-test/r/named_pipe.result'' mysql-test/t/named_pipe-master.opt: New BitKeeper file ``mysql-test/t/named_pipe-master.opt'' mysql-test/t/named_pipe.test: New BitKeeper file ``mysql-test/t/named_pipe.test''
2007-09-24 12:42:44 +02:00
# Only run this test if named pipe is avaliable
let $nmp= query_get_value("SHOW VARIABLES LIKE 'named_pipe'", Value, 1);
Tests: many if/while expresissons simplified after 57276
2010-11-17 11:16:13 +01:00
if ($nmp != ON){
Add test for named pipes on windows Improve test for shm on windows mysql-test/include/windows.inc: improve "skip message" and don't require a result file mysql-test/r/shm.result: Update result after adding more tests mysql-test/t/shm-master.opt: Add $MTR_BUILD_THREAD to get a unique shared memory base name mysql-test/t/shm.test: Run a bunch of more test to check shm mysql-test/r/named_pipe.result: New BitKeeper file ``mysql-test/r/named_pipe.result'' mysql-test/t/named_pipe-master.opt: New BitKeeper file ``mysql-test/t/named_pipe-master.opt'' mysql-test/t/named_pipe.test: New BitKeeper file ``mysql-test/t/named_pipe.test''
2007-09-24 12:42:44 +02:00
skip No named pipe support;
}
Bug #47423 mtr connects to wrong database The reason for the bug is that mysqtest as well as other client tools running in test suite (mysqlbinlog, mysqldump) will first try to connect whatever database has created shared memory with default base name "MySQL" and use this. (Same effect could be seen on Unix if mtr would not care to calculate "port" and "socket" parameter). The fix ensures that all client tools and running in mtr use unique per-database shared memory base parameters, so there is no possibility to clash with already installed one. We use socket name for shared memory base (it's known to be unique). This shared-memory-base is written to the MTR config file to the [client] and [mysqld] sections. Fix made also made sure all client tools understand and correctly handle --shared-memory-base. Prior to this patch it was not the case for mysqltest, mysqlbinlog and mysql_client_test. All new connections done from mtr scripts via connect() will by default set shared-memory-base. And finally, there is a possibility to force shared memory or pipe connection and overwrite shared memory/pipe base name from within mtr scripts via optional PIPE or SHM modifier. This functionality was manually backported from 6.0 (original patch http://lists.mysql.com/commits/74749)
2009-11-03 01:19:37 +01:00
# Connect using named pipe for testing
connect(pipe_con,localhost,root,,,,,PIPE);
Add test for named pipes on windows Improve test for shm on windows mysql-test/include/windows.inc: improve "skip message" and don't require a result file mysql-test/r/shm.result: Update result after adding more tests mysql-test/t/shm-master.opt: Add $MTR_BUILD_THREAD to get a unique shared memory base name mysql-test/t/shm.test: Run a bunch of more test to check shm mysql-test/r/named_pipe.result: New BitKeeper file ``mysql-test/r/named_pipe.result'' mysql-test/t/named_pipe-master.opt: New BitKeeper file ``mysql-test/t/named_pipe-master.opt'' mysql-test/t/named_pipe.test: New BitKeeper file ``mysql-test/t/named_pipe.test''
2007-09-24 12:42:44 +02:00
# Source select test case
-- source include/common-tests.inc
Bug #47423 mtr connects to wrong database The reason for the bug is that mysqtest as well as other client tools running in test suite (mysqlbinlog, mysqldump) will first try to connect whatever database has created shared memory with default base name "MySQL" and use this. (Same effect could be seen on Unix if mtr would not care to calculate "port" and "socket" parameter). The fix ensures that all client tools and running in mtr use unique per-database shared memory base parameters, so there is no possibility to clash with already installed one. We use socket name for shared memory base (it's known to be unique). This shared-memory-base is written to the MTR config file to the [client] and [mysqld] sections. Fix made also made sure all client tools understand and correctly handle --shared-memory-base. Prior to this patch it was not the case for mysqltest, mysqlbinlog and mysql_client_test. All new connections done from mtr scripts via connect() will by default set shared-memory-base. And finally, there is a possibility to force shared memory or pipe connection and overwrite shared memory/pipe base name from within mtr scripts via optional PIPE or SHM modifier. This functionality was manually backported from 6.0 (original patch http://lists.mysql.com/commits/74749)
2009-11-03 01:19:37 +01:00
connection default;
disconnect pipe_con;
MDEV-10383 Named pipes : multiple servers can listen on the same pipename Use FILE_FLAG_FIRST_PIPE_INSTANCE with the first CreateNamedPipe() call to make sure the pipe does not already exist.
2016-08-02 18:52:51 +02:00
# MDEV-10383 : check that other server cannot 'bind' on the same pipe
let $MYSQLD_DATADIR= `select @@datadir`;
--error 1
--exec $MYSQLD_CMD --enable-named-pipe --skip-networking --log-error=second-mysqld.err
let SEARCH_FILE=$MYSQLD_DATADIR/second-mysqld.err;
let SEARCH_PATTERN=\[ERROR\] Create named pipe failed;
source include/search_pattern_in_file.inc;
MDEV-23279 main.named_pipe test timeouts if called twice in a row The test timeouts, because mtr is waiting for pid file. The pid file is not there, because expected to fail mysqld startup (duplicate named pipe name), this startup removed pid file of the running mysqld instance. To fix, split handle_connections_win() into the initialization part, and accept/handle part, like it is done elsewhere. The initialization part runs before pid file handling, and aborts on errors , thus avoiding pid file overwrites.
2020-08-10 17:33:48 +00:00
remove_file $SEARCH_FILE;
Reference in a new issue Copy permalink