Blame SOURCES/mariadb-install-test.patch

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