mariadb/mysql-test
Andrei Elkin 04d72f8682 Bug#38934 slave slave until does not work with --replicate-same-server-id
Bug#38540 rpl_server_id2 uses show slave status unnecessarily
            
Slave did not perform any event recorded into the relay log from some
different master when it was started with --replicate-same-server-id.
The reason appeared to be a consequence of BUG#38734 which stopped the
sql thread at its startup time.
      
The real fixes for the current bug are in the patch for BUG#38734.
This changeset carries only a regression test for the bugs.  Bug#38540
gets fixed too by means of eliminating an extra show slave status.
2008-12-19 20:59:22 +02:00
..
extra BUG#38350: Many tests don't clean up after themselves on exit. 2008-11-13 20:19:00 +01:00
include Merge 2008-12-05 22:15:52 +01:00
lib Bug #40924 please print timestamp when mtr fails 2008-12-03 14:11:03 +01:00
r Bug#40145. Argument for LOAD_FILE() can be too long and sometimes 2008-11-27 15:15:14 +03:00
std_data Merge 5.1 main -> 5.1-rpl 2008-09-06 08:51:17 +08:00
suite Bug#38934 slave slave until does not work with --replicate-same-server-id 2008-12-19 20:59:22 +02:00
t BUG#41018: innodb_max_dirty_pages_pct_func fails sporadically: error 28 from storage engine 2008-12-02 20:07:18 +01:00
Makefile.am WL#4189 Add full backward compatibility to mysql-test-run.pl 2008-11-14 09:45:32 +01:00
mysql-stress-test.pl
mysql-test-run.pl Clarified the error message printed when mtr's test cleanup check fails. 2008-11-25 17:51:02 +01:00
purify.supp
README
README.gcov
README.stress
valgrind.supp Bug #38693: leaked memory with blobs! 2008-10-15 16:55:52 +03:00

This directory contains a test suite for the MySQL daemon. To run
the currently existing test cases, simply execute ./mysql-test-run in
this directory. It will fire up the newly built mysqld and test it.

Note that you do not have to have to do "make install", and you could
actually have a co-existing MySQL installation. The tests will not
conflict with it.

All tests must pass. If one or more of them fail on your system, please
read the following manual section for instructions on how to report the
problem:

http://dev.mysql.com/doc/mysql/en/mysql-test-suite.html

If you want to use an already running MySQL server for specific tests,
use the --extern option to mysql-test-run. Please note that in this mode,
the test suite expects you to provide the names of the tests to run.
For example, here is the command to run the "alias" and "analyze" tests
with an external server:

mysql-test-run --extern alias analyze

To match your setup, you might also need to provide --socket, --user, and
other relevant options.

With no test cases named on the command line, mysql-test-run falls back
to the normal "non-extern" behavior. The reason for this is that some
tests cannot run with an external server.


You can create your own test cases. To create a test case, create a new
file in the t subdirectory using a text editor. The file should have a .test
extension. For example:

 xemacs t/test_case_name.test

 In the file, put a set of SQL statements that create some tables,
 load test data, and run some queries to manipulate it.

 We would appreciate it if you name your test tables t1, t2, t3 ... (to not
 conflict too much with existing tables).

 Your test should begin by dropping the tables you are going to create and
 end by dropping them again.  This ensures that you can run the test over
 and over again.
 
 If you are using mysqltest commands (like result file names) in your
 test case, you should create the result file as follows:

 mysql-test-run --record test_case_name

 or

 mysqltest --record < t/test_case_name.test

 If you only have a simple test cases consisting of SQL statements and
 comments, you can create the test case in one of the following ways:

 mysql-test-run --record test_case_name

 mysql test < t/test_case_name.test > r/test_case_name.result

 mysqltest --record --record-file=r/test_case_name.result < t/test_case_name.test

 When this is done, take a look at r/test_case_name.result
 - If the result is incorrect, you have found a bug. In this case, you should
   edit the test result to the correct results so that we can verify
   that the bug is corrected in future releases.

To submit your test case, put your .test file and .result file(s) into
a tar.gz archive, add a README that explains the problem, ftp the 
archive to ftp://support.mysql.com/pub/mysql/secret/ and send a mail
to bugs@lists.mysql.com