mirror/mariadb
1
0
Fork 0
mirror of https://github.com/MariaDB/server.git synced 2025-01-19 13:32:33 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
mariadb/mysql-test
History
unknown 292f91e83d Simplified a test. 
thd->enter_cond() and exit_cond(), so that the I/O thread accepts to stop
when it's waiting for relay log space.
Reset ignore_log_space_limit to 0 when the SQL thread terminates.


mysql-test/r/rpl_relayspace.result:
  result update
mysql-test/t/rpl_relayspace-slave.opt:
  smaller relay_log_space_limit to speed up things.
mysql-test/t/rpl_relayspace.test:
  Less queries in the test, to make it simpler.
  Testcase if the IO thread blocked in wait_for_relay_log_space
  accepts to stop when STOP SLAVE.
sql/slave.cc:
  thd->enter_cond() and exit_cond(), so that the I/O thread accepts to stop
  when it's waiting on cond (waiting for relay log space).
  Reset ignore_log_space_limit to 0 when the SQL thread terminates.
2003-06-15 12:01:51 +02:00
..
include Openssl test 2003-03-11 13:41:53 +04:00
misc Fixed that LOAD DATA INFILE works with transactions. 2001-08-28 06:43:55 +03:00
r Simplified a test. 2003-06-15 12:01:51 +02:00
std_data Merge eagle.mysql.r18.ru:/home/vva/work/mysql.orig/clear/mysql-4.0 2003-05-21 14:58:11 -04:00
t Simplified a test. 2003-06-15 12:01:51 +02:00
create-test-result Removed not used functions from sql_cache 2001-12-14 16:02:41 +02:00
fix-result fixed problem in rpl_log test 2001-11-19 12:03:30 -07:00
install_test_db.sh Added CREATE TEMPORARY TABLES and LOCK TABLES to db and host tables 2002-09-16 15:55:19 +03:00
Makefile.am - added missing file mysql-test/std_data/des_key_file to source and binary 2003-03-04 18:18:05 +01:00
mysql-test-run.sh Merge gbichot@213.136.52.20:/home/bk/mysql-4.0 2003-06-10 23:31:09 +02:00
README
README.gcov
resolve-stack Here comes a nasty patch, although I am not ready to push it yet. I will 2002-01-19 19:16:52 -07:00

README 

This directory contains a test suite for 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 of how to report the problem:

http://www.mysql.com/doc/M/y/MySQL_test_suite.html


You can create your own test cases. To create a test case:

 cd t
 vi test_case_name.test

 in the file, put a set of SQL commands that will create some tables,
 load test data, run some queries to manipulate it.

 We would appreciate if the test tables were called 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 will ensure that one can run the test
 over and over again.
 
 If you are using mysqltest commands (like result file names) in your
 test case you should do 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 consistent of SQL commands and comments
 you can create the test case 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 wrong, 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