ganapathi / rpms / mariadb

Forked from rpms/mariadb 4 years ago
Clone

Blame SOURCES/mariadb-install-test.patch

031387
Improve the documentation that will be installed in the mysql-test RPM.
031387
031387
diff -up mariadb-5.5.32/mysql-test/README.p3 mariadb-5.5.32/mysql-test/README
031387
--- mariadb-5.5.32/mysql-test/README.p3	2013-07-17 16:51:29.000000000 +0200
031387
+++ mariadb-5.5.32/mysql-test/README	2013-07-30 23:22:54.959494478 +0200
031387
@@ -1,15 +1,28 @@
031387
-This directory contains a test suite for the MySQL daemon. To run
031387
-the currently existing test cases, simply execute ./mysql-test-run in
031387
-this directory. It will fire up the newly built mysqld and test it.
031387
-
031387
-Note that you do not have to have to do "make install", and you could
031387
-actually have a co-existing MySQL installation. The tests will not
031387
-conflict with it. To run the test suite in a source directory, you
031387
-must do make first.
031387
-
031387
-All tests must pass. If one or more of them fail on your system, please
031387
-read the following manual section for instructions on how to report the
031387
-problem:
031387
+This directory contains a test suite for the MariaDB daemon. To run
031387
+the currently existing test cases, execute ./mysql-test-run in
031387
+this directory.
031387
+
031387
+For use in Red Hat distributions, you should run the script as user mysql,
031387
+who is created with nologin shell however, so the best bet is something like
031387
+       $ su -
031387
+       # cd /usr/share/mysql-test
031387
+       # su -s /bin/bash mysql -c "./mysql-test-run --skip-test-list=rh-skipped-tests.list"
031387
+
031387
+This will use the installed mysql executables, but will run a private copy
031387
+of the server process (using data files within /usr/share/mysql-test),
031387
+so you need not start the mysqld service beforehand.
031387
+
031387
+The "--skip-test-list=rh-skipped-tests.list" option excludes tests that are
031387
+known to fail on one or more Red-Hat-supported platforms.  You can omit it
031387
+if you want to check whether such failures occur for you.  Documentation
031387
+about the reasons for omitting such tests can be found in the file
031387
+rh-skipped-tests.list.
031387
+
031387
+To clean up afterwards, remove the created "var" subdirectory, eg
031387
+       # su -s /bin/bash - mysql -c "rm -rf /usr/share/mysql-test/var"
031387
+
031387
+If one or more tests fail on your system, please read the following manual
031387
+section for instructions on how to report the problem:
031387
 
031387
 http://kb.askmonty.org/v/reporting-bugs
031387
 
031387
@@ -26,7 +39,8 @@ other relevant options.
031387
 
031387
 With no test cases named on the command line, mysql-test-run falls back
031387
 to the normal "non-extern" behavior. The reason for this is that some
031387
-tests cannot run with an external server.
031387
+tests cannot run with an external server (because they need to control the
031387
+options with which the server is started).
031387
 
031387
 You can create your own test cases. To create a test case, create a new
031387
 file in the t subdirectory using a text editor. The file should have a .test