Blame SOURCES/mariadb-install-test.patch

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