1MYSQL-TEST-RUN() MYSQL-TEST-RUN()
2
6 mysql-test-run.pl - run MariaDB test suite
7
9 mysql-test-run.pl [options]
10
12 The mysql-test-run.pl Perl script is the main application used to run
13 the MariaDB test suite. It invokes mysqltest to run individual test
14 cases.
15 Invoke mysql-test-run.pl in the mysql-test directory like this:
17 shell> mysql-test-run.pl [options] [test_name] ...
19 Each test_name argument names a test case. The test case file that
21 corresponds to the test name is t/test_name.test.
22 For each test_name argument, mysql-test-run.pl runs the named test
24 case. With no test_name arguments, mysql-test-run.pl runs all .test
25 files in the t subdirectory.
26 If no suffix is given for the test name, a suffix of .test is assumed.
28 Any leading path name is ignored. These commands are equivalent:
29 shell> mysql-test-run.pl mytest
31 shell> mysql-test-run.pl mytest.test
32 shell> mysql-test-run.pl t/mytest.test
33 A suite name can be given as part of the test name. That is, the syntax
35 for naming a test is:
36 [suite_name.]test_name[.suffix]
38 If a suite name is given, mysql-test-run.pl looks in that suite for the
40 test. The test file corresponding to a test named suite_name.test_name
41 is found in suite/suite_name/t/test_name.test. There is also an
42 implicit suite name main for the tests in the top t directory. With no
43 suite name, mysql-test-run.pl looks in the default list of suites for a
44 match and runs the test in any suites where it finds the test. Suppose
45 that the default suite list is main, binlog, rpl, and that a test
46 mytest.test exists in the main and rpl suites. With an argument of
47 mytest or mytest.test, mysql-test-run.pl will run mytest.test from the
48 main and rpl suites.
49 To run a family of test cases for which the names share a common
51 prefix, use the --do-test=prefix option. For example, --do-test=rpl
52 runs the replication tests (test cases that have names beginning with
53 rpl). --skip-test has the opposite effect of skipping test cases for
54 which the names share a common prefix.
55 The argument for the --do-test and --skip-test options also allows more
57 flexible specification of which tests to perform or skip. If the
58 argument contains a pattern metacharacter other than a lone period, it
59 is interpreted as a Perl regular expression and applies to test names
60 that match the pattern. If the argument contains a lone period or does
61 not contain any pattern metacharacters, it is interpreted the same way
62 as previously and matches test names that begin with the argument
63 value. For example, --do-test=testa matches tests that begin with
64 testa, --do-test=main.testa matches tests in the main test suite that
65 begin with testa, and --do-test=main.*testa matches test names that
66 contain main followed by testa with anything in between. In the latter
67 case, the pattern match is not anchored to the beginning of the test
68 name, so it also matches names such as xmainytesta.
69 To perform setup prior to running tests, mysql-test-run.pl needs to
71 invoke mysqld with the --bootstrap and --skip-grant-tables options. If
72 MySQL was configured with the --disable-grant-options option,
73 --bootstrap, --skip-grant-tables, and --init-file will be disabled. To
74 handle this, set the MYSQLD_BOOTSTRAP environment variable to the full
75 path name of a server that has all options enabled. mysql-test-run.pl
76 will use that server to perform setup; it is not used to run the tests.
77 The init_file test will fail if --init-file is disabled. This is an
79 expected failure that can be handled as follows:
80 shell> export MYSQLD_BOOTSTRAP
82 shell> MYSQLD_BOOTSTRAP=/full/path/to/mysqld
83 shell> make test force="--skip-test=init_file"
84 To run mysql-test-run.pl on Windows, you´ll need either Cygwin or
86 ActiveState Perl to run it. You may also need to install the modules
87 required by the script. To run the test script, change location into
88 the mysql-test directory, set the MTR_VS_CONFIG environment variable to
89 the configuration you selected earlier (or use the --vs-config option),
90 and invoke mysql-test-run.pl. For example (using Cygwin and the bash
91 shell):
92 shell> cd mysql-test
94 shell> export MTR_VS_CONFIG=debug
95 shell> ./mysqltest-run.pl --force --timer
96 shell> ./mysqltest-run.pl --force --timer --ps-protocol
97 mysql-test-run.pl uses several environment variables. Some of them are
99 listed in the following table. Some of these are set from the outside
100 and used by mysql-test-run.pl, others are set by mysql-test-run.pl
101 instead, and may be referred to in tests.
102 ┌─────────────────┬────────────────────────────────────┐
104 │Variable │ Meaning │
105 ├─────────────────┼────────────────────────────────────┤
106 │MTR_VERSION │ If set to 1, will run the │
107 │ │ older version 1 of │
108 │ │ mysql-test-run.pl. │
109 │ │ This will affect │
110 │ │ what │
111 │ │ functionailty is available │
112 │ │ and what command line │
113 │ │ options │
114 │ │ are supported. │
115 ├─────────────────┼────────────────────────────────────┤
116 │MTR_MEM │ If set to anything, will run tests │
117 │ │ with files in "memory" using tmpfs │
118 │ │ or │
119 │ │ ramdisk. Not │
120 │ │ available on Windows. Same as │
121 │ │ --mem option │
122 ├─────────────────┼────────────────────────────────────┤
123 │MTR_PARALLEL │ If set, defines number of parallel │
124 │ │ threads executing tests. Same as │
125 │ │ --parallel option │
126 ├─────────────────┼────────────────────────────────────┤
127 │MTR_BUILD_THREAD │ If set, defines which port number │
128 │ │ range is used for the server │
129 ├─────────────────┼────────────────────────────────────┤
130 │MTR_PORT_BASE │ If set, defines which port number │
131 │ │ range is used for the server │
132 ├─────────────────┼────────────────────────────────────┤
133 │MTR_NAME_TIMEOUT │ Setting of a timeout in minutes or │
134 │ │ seconds, corresponding to command │
135 │ │ line option │
136 │ │ --name-timeout. │
137 │ │ Available timeout │
138 │ │ names are TESTCASE, │
139 │ │ SUITE (both in │
140 │ │ minutes) and │
141 │ │ START, SHUTDOWN │
142 │ │ (both in seconds). │
143 │ │ These variables are supported from │
144 │ │ MySQL 5.1.44. │
145 ├─────────────────┼────────────────────────────────────┤
146 │MYSQL_TEST │ Path name to mysqltest binary │
147 ├─────────────────┼────────────────────────────────────┤
148 │MYSQLD_BOOTSTRAP │ Full path name to mysqld that has │
149 │ │ all options enabled │
150 ├─────────────────┼────────────────────────────────────┤
151 │MYSQLTEST_VARDIR │ Path name to the var directory │
152 │ │ that is used for │
153 │ │ logs, temporary │
154 │ │ files, and so forth │
155 ├─────────────────┼────────────────────────────────────┤
156 │MYSQL_TEST_DIR │ Full path to the mysql-test │
157 │ │ directory where tests │
158 │ │ are being run from │
159 ├─────────────────┼────────────────────────────────────┤
160 │MYSQL_TMP_DIR │ Path to temp directory used for │
161 │ │ temporary files during tests │
162 └─────────────────┴────────────────────────────────────┘
163 The variable MTR_PORT_BASE was added in MySQL 5.1.45 as a more logical
165 replacement for MTR_BUILD_THREAD. It gives the actual port number
166 directly (will be rounded down to a multiple of 10). If you use
167 MTR_BUILD_THREAD, the port number is found by multiplying this by 10
168 and adding 10000.
169 Tests sometimes rely on certain environment variables being defined.
171 For example, certain tests assume that MYSQL_TEST is defined so that
172 mysqltest can invoke itself with exec $MYSQL_TEST.
173 Other tests may refer to the last three variables listed in the
175 preceding table, to locate files to read or write. For example, tests
176 that need to create files will typically put them in
177 $MYSQL_TMP_DIR/file_name.
178 If you are running mysql-test-run.pl version 1 by setting MTR_VERSION,
180 note that this only affects the test driver, not the test client (and
181 its language) or the tests themselves.
182 A few tests might not run with version 1 because they depend on some
184 feature of version 2. You may have those tests skipped by adding the
185 test name to the file lib/v1/incompatible.tests. This feature is
186 available from MySQL 5.1.40.
187 mysql-test-run.pl supports the options in the following list. An
189 argument of -- tells mysql-test-run.pl not to process any following
190 arguments as options.
191 · --help, -h
193 Display a help message and exit.
195 · --big-test
197 Allow tests marked as "big" to run. Tests can be thus marked by
199 including the line --source include/big_test.inc, and they will
200 only be run if this option is given, or if the environment variable
201 BIG_TEST is set to 1. Repeat this option twice to run only "big"
202 tests.
203 This is typically used for tests that take a very long to run, or
205 that use many resources, so that they are not suitable for running
206 as part of a normal test suite run.
207 · --boot-dbx
209 Run the mysqld server used for bootstrapping the database through
211 the dbx debugger.
212 · --boot-ddd
214 Run the mysqld server used for bootstrapping the database through
216 the ddd debugger.
217 · --boot-gdb
219 Run the mysqld server used for bootstrapping the database through
221 the gdb debugger.
222 · --[mtr-]build-thread=number
224 Specify a number to calculate port numbers from. The formula is 10
226 * build_thread + 10000. Instead of a number, it can be set to auto,
227 which is also the default value, in which case mysql-test-run.pl
228 will allocate a number unique to this host.
229 The value (number or auto) can also be set with the
231 MTR_BUILD_THREAD environment variable.
232 The more logical --port-base is supported as an alternative.
234 · --callgrind
236 Instructs valgrind to use callgrind.
238 · --check-testcases
240 Check test cases for side effects. This is done by checking system
242 state before and after each test case; if there is any difference,
243 a warning to that effect will be written, but the test case will
244 not be marked as failed because of it. This check is enabled by
245 default.
246 · --client-bindir=path
248 The path to the directory where client binaries are located.
250 · --client-dbx
252 Start mysqltest in the dbx debugger.
254 · --client-ddd
256 Start mysqltest in the ddd debugger.
258 · --client-debugger=debugger
260 Start mysqltest in the named debugger.
262 · --client-gdb
264 Start mysqltest in the gdb debugger.
266 · --client-libdir=path
268 The path to the directory where client libraries are located.
270 · --combination=value
272 Extra options to pass to mysqld. The value should consist of one or
274 more comma-separated mysqld options. This option is similar to
275 --mysqld but should be given two or more times. mysql-test-run.pl
276 executes multiple test runs, using the options for each instance of
277 --combination in successive runs. If --combination is given only
278 once, it has no effect. For test runs specific to a given test
279 suite, an alternative to the use of --combination is to create a
280 combinations file in the suite directory. The file should contain a
281 section of options for each test run.
282 · --comment=str
284 Write str to the output within lines filled with #, as a form of
286 banner.
287 · --compress
289 Compress all information sent between the client and the server if
291 both support compression.
292 · --cursor-protocol
294 Use the cursor protocol between client and server (implies
296 --ps-protocol).
297 · --dbx
299 Start the mysqld(s) in the dbx debugger.
301 · --ddd
303 Start the mysqld(s) in the ddd debugger.
305 · --debug
307 Dump trace output for all clients and servers.
309 · --debug-common
311 Same as --debug, but sets the 'd' debug flags to
313 "query,info,error,enter,exit".
314 · --debug-server
316 Use debug version of server, but without turning on tracing.
318 · --debugger=debugger
320 Start mysqld using the named debugger.
322 · --debug-sync-timeout=N
324 Controls whether the Debug Sync facility for testing and debugging
326 is enabled. The option value is a timeout in seconds. The default
327 value is 300. A value of 0 disables Debug Sync. The value of this
328 option also becomes the default timeout for individual
329 synchronization points.
330 mysql-test-run.pl passes --loose-debug-sync-timeout=N to mysqld.
332 The --loose prefix is used so that mysqld does not fail if Debug
333 Sync is not compiled in.
334 · --defaults-file=file_name
336 Use the named file as fixed config file template for all tests.
338 · --defaults_extra_file=file_name
340 Add setting from the named file to all generated configs.
342 · --do-test=prefix|regex
344 Run all test cases having a name that begins with the given prefix
346 value, or fulfils the regex. This option provides a convenient way
347 to run a family of similarly named tests.
348 The argument for the --do-test option also allows more flexible
350 specification of which tests to perform. If the argument contains a
351 pattern metacharacter other than a lone period, it is interpreted
352 as a Perl regular expression and applies to test names that match
353 the pattern. If the argument contains a lone period or does not
354 contain any pattern metacharacters, it is interpreted the same way
355 as previously and matches test names that begin with the argument
356 value. For example, --do-test=testa matches tests that begin with
357 testa, --do-test=main.testa matches tests in the main test suite
358 that begin with testa, and --do-test=main.*testa matches test names
359 that contain main followed by testa with anything in between. In
360 the latter case, the pattern match is not anchored to the beginning
361 of the test name, so it also matches names such as xmainytestz.
362 · --dry-run
364 Don't run any tests, print the list of tests that were selected for
366 execution.
367 · --embedded-server
369 Use a version of mysqltest built with the embedded server.
371 · --enable-disabled
373 Ignore any disabled.def file, and also run tests marked as
375 disabled. Success or failure of those tests will be reported the
376 same way as other tests.
377 · --experimental=file_name
379 Specify a file that contains a list of test cases that should be
381 displayed with the [ exp-fail ] code rather than [ fail ] if they
382 fail.
383 For an example of a file that might be specified via this option,
385 see mysql-test/collections/default.experimental.
386 · --extern option=value
388 Use an already running server. The option/value pair is what is
390 needed by the mysql client to connect to the server. Each --extern
391 option can only take one option/value pair as an argument, so you
392 need to repeat --extern for each pair needed. Example:
393 ./mysql-test-run.pl --extern socket=var/tmp/mysqld.1.sock alias
395 Note: If a test case has an .opt file that requires the server to
397 be restarted with specific options, the file will not be used. The
398 test case likely will fail as a result.
399 · --fast
401 Do not perform controlled shutdown when servers need to be
403 restarted or at the end of the test run. This is equivalent to
404 using --shutdown-timeout=0.
405 · --force-restart
407 Always restart servers between tests.
409 · --force
411 Normally, mysql-test-run.pl exits if a test case fails. --force
413 causes execution to continue regardless of test case failure.
414 · --gcov
416 Collect coverage information after the test. The result is a gcov
418 file per source and header file.
419 · --gcov-src-dir
421 Colllect coverage only within the given subdirectory. For example,
423 if you're only developing the SQL layer, it makes sense to use
424 --gcov-src-dir=sql.
425 · --gdb
427 Start the mysqld(s) in the gdb debugger.
429 · --gprof
431 Collect profiling information using the gprof profiling tool.
433 · --manual-dbx
435 Use a server that has already been started by the user in the dbx
437 debugger.
438 · --manual-ddd
440 Use a server that has already been started by the user in the ddd
442 debugger.
443 · --manual-debug
445 Use a server that has already been started by the user in a
447 debugger.
448 · --manual-gdb
450 Use a server that has already been started by the user in the gdb
452 debugger.
453 · --manual-lldb
455 Use a server that has already been started by the user in the lldb
457 debugger.
458 · --mark-progress
460 Marks progress with timing (in milliseconds) and line number in
462 var/log/testname.progress.
463 · --max-connections=num
465 The maximum number of simultaneous server connections that may be
467 used per test. If not set, the maximum is 128. Minimum allowed
468 limit is 8, maximum is 5120. Corresponds to the same option for
469 mysqltest.
470 · --max-save-core=N
472 Limit the number of core files saved, to avoid filling up disks in
474 case of a frequently crashing server. Defaults to 5, set to 0 for
475 no limit. May also be set with the environment variable
476 MTR_MAX_SAVE_CORE
477 · --max-save-datadir=N
479 Limit the number of data directories saved after failed tests, to
481 avoid filling up disks in case of frequent failures. Defaults to
482 20, set to 0 for no limit. May also be set with the environment
483 variable MTR_MAX_SAVE_DATADIR
484 · --max-test-fail=N
486 Stop execution after the specified number of tests have failed, to
488 avoid using up resources (and time) in case of massive failures.
489 retries are not counted, nor are failures of tests marked
490 experimental. Defaults to 10, set to 0 for no limit. May also be
491 set with the environment variable MTR_MAX_TEST_FAIL
492 · --mem
494 This option is not supported on Windows.
496 Run the test suite in memory, using tmpfs or ramdisk. This can
498 decrease test times significantly, in particular if you would
499 otherwise be running over a remote file system. mysql-test-run.pl
500 attempts to find a suitable location using a built-in list of
501 standard locations for tmpfs and puts the var directory there. This
502 option also affects placement of temporary files, which are created
503 in var/tmp.
504 The default list includes /dev/shm. You can also enable this option
506 by setting the environment variable MTR_MEM[=dir_name]. If dir_name
507 is given, it is added to the beginning of the list of locations to
508 search, so it takes precedence over any built-in locations.
509 Once you have run tests with --mem within a mysql-testdirectory, a
511 soflink var will have been set up to the temporary directory, and
512 this will be re-used the next time, until the soflink is deleted.
513 Thus, you do not have to repeat the --mem option next time.
514 · --mysqld=value
516 Extra options to pass to mysqld. The value should consist of one or
518 more comma-separated mysqld options.
519 · --mysqld-env=VAR=VAL
521 Specify additional environment settings for "mysqld". Use
523 additional --mysqld-env options to set more than one variable.
524 · --nocheck-testcases
526 Disable the check for test case side effects; see --check-testcases
528 for a description.
529 · --noreorder
531 Do not reorder tests to reduce number of restarts, but run them in
533 exactly the order given. If a whole suite is to be run, the tests
534 are run in alphabetical order, though similar combinations will be
535 grouped together. If more than one suite is listed, the tests are
536 run one suite at a time, in the order listed.
537 · --notimer
539 Cause mysqltest not to generate a timing file. The effect of this
541 is that the report from each test case does not include the timing
542 in milliseconds as it normally does.
543 · --nowarnings
545 Do not look for and report errors and warning in the server logs.
547 · --parallel={N|auto}
549 Run tests using N parallel threads. By default, 1 thread is used.
551 Use --parallel=auto for auto-setting of N.
552 · --[mtr-]port-base=P
554 Specify base of port numbers to be used; a block of 10 will be
556 allocated. P should be divisible by 10; if it is not, it will be
557 rounded down. If running with more than one parallel test thread,
558 thread 2 will use the next block of 10 and so on.
559 If the port number is given as auto, which is also the default,
561 mysql-test-run.pl will allocate a number unique to this host. The
562 value may also be given with the environment variable
563 MTR_PORT_BASE.
564 If both --build-thread and --port-base are used, --port-base takes
566 precedence.
567 · --print-testcases
569 Do not run any tests, but print details about all tests, in the
571 order they would have been run.
572 · --ps-protocol
574 Use the binary protocol between client and server.
576 · --record
578 Pass the --record option to mysqltest. This option requires a
580 specific test case to be named on the command line.
581 · --reorder
583 Reorder tests to minimize the number of server restarts needed.
585 This is the default behavior. There is no guarantee that a
586 particular set of tests will always end up in the same order.
587 · --repeat=N
589 Run each test N number of times.
591 · --report-features
593 First run a "test" that reports MariaDB features, displaying the
595 output of SHOW ENGINES and SHOW VARIABLES. This can be used to
596 verify that binaries are built with all required features.
597 · --report-times
599 Report how much time has been spent on different phases of test
601 execution.
602 · --retry=N
604 If a test fails, it is retried up to a maximum of N runs (default
606 1). Retries are also limited by the maximum number of failures
607 before stopping, set with the --retry-failure option. This option
608 has no effect unless --force is also used; without it, test
609 execution will terminate after the first failure.
610 The --retry and --retry-failure options do not affect how many
612 times a test repeated with --repeat may fail in total, as each
613 repetition is considered a new test case, which may in turn be
614 retried if it fails.
615 · --retry-failure=N
617 When using the --retry option to retry failed tests, stop when N
619 failures have occurred (default 2). Setting it to 0 or 1
620 effectively turns off retries.
621 · --shutdown-timeout=SECONDS
623 Max number of seconds to wait for servers to do controlled shutdown
625 before killing them. Default is 10.
626 · --skip-combinations
628 Do not apply combinations; ignore combinations file or option.
630 · --skip-rpl
632 Skip replication test cases.
634 · --skip-ssl
636 Do not start mysqld with support for SSL connections.
638 · --skip-test=regex|regex
640 Specify a regular expression to be applied to test case names.
642 Cases with names that match the expression are skipped. tests to
643 skip.
644 The argument for the --skip-test option allows more flexible
646 specification of which tests to skip. If the argument contains a
647 pattern metacharacter other than a lone period, it is interpreted
648 as a Perl regular expression and applies to test names that match
649 the pattern. See the description of the --do-test option for
650 details.
651 · --skip-test-list=FILE
653 Skip the tests listed in FILE. Each line in the file is an entry
655 and should be formatted as: <TESTNAME> : <COMMENT>
656 · --skip-*
658 --skip-* options not otherwise recognized by mysql-test-run.pl are
660 passed to the master server.
661 · --sleep=N
663 Pass --sleep=N to mysqltest.
665 · --sp-protocol
667 Create a stored procedure to execute all queries.
669 · --ssl
671 If mysql-test-run.pl is started with the --ssl option, it sets up a
673 secure connection for all test cases. In this case, if mysqld does
674 not support SSL, mysql-test-run.pl exits with an error message:
675 Couldn´t find support for SSL
676 · --staging-run
678 Run a limited number of tests (no slow tests). Used for running
680 staging trees with valgrind.
681 · --start
683 Initialize and start servers with the startup settings for the
685 specified test case. You can use this option to start a server to
686 which you can connect later. For example, after building a source
687 distribution you can start a server and connect to it with the
688 mysql client like this:
689 shell> cd mysql-test
691 shell> ./mysql-test-run.pl --start alias &
692 shell> ../mysql -S ./var/tmp/master.sock -h localhost -u root
693 If no tests are named on the command line, the server(s) will be
695 started with settings for the first test that would have been run
696 without the --start option.
697 mysql-test-run.pl will stop once the server has been started, but
699 will terminate if the server dies. If killed, it will also shut
700 down the server.
701 · --start-and-exit
703 Same --start, but mysql-test-run terminates and leaves just the
705 server running.
706 · --start-dirty
708 This is similar to --start, but will skip the database
710 initialization phase and assume that database files are already
711 available. Usually this means you must have run another test first.
712 · --start-from=test_name
714 mysql-test-run.pl sorts the list of names of the test cases to be
716 run, and then begins with test_name.
717 · --strace
719 Run the "mysqld" executables using strace. Default options are -f
721 -o var/log/'mysqld-name'.strace.
722 · --strace-client
724 Create strace output for mysqltest, optionally specifying name and
726 path to the trace program to use.
727 Example: ./mysql-test-run.pl --strace-client=ktrace
729 · --strace-option=ARGS
731 Option to give strace, replaces default option(s).
733 · --stress=ARGS
735 Run stress test, providing options to mysql-stress-test.pl. Options
737 are separated by comma.
738 · --suite[s]=suite_name...
740 Comma separated list of suite names to run. The default is:
742 "main-,archive-,binlog-,csv-,federated-,funcs_1-,funcs_2-,
743 handler-,heap-,innodb-,innodb_fts-,innodb_zip-,maria-,
744 multi_source-,optimizer_unfixed_bugs-,parts-,perfschema-,
745 plugins-,roles-,rpl-,sys_vars-,unit-,vcol-".
746 · --stop-file=file
748 If this file is detected, mysqltest will not start new tests until
750 the file is removed (also MTR_STOP_FILE environment variable).
751 · --stop-keep-alive=sec
753 Works with --stop-file, print messages every sec seconds when
755 mysqltest is waiting to remove the file (for buildbot) (also
756 MTR_STOP_KEEP_ALIVE environment variable).
757 · --suite-timeout=minutes
759 Specify the maximum test suite runtime in minutes. The default is
761 360.
762 · --testcase-timeout
764 Specify the maximum test case runtime in minutes. The default is
766 15.
767 · --timediff
769 Used with --timestamp, also print time passed since the previous
771 test started.
772 · --timer
774 Cause mysqltest to generate a timing file. The default file is
776 named ./var/log/timer.
777 · --timestamp
779 Prints a timestamp before the test case name in each test report
781 line, showing when the test ended.
782 · --tmpdir=path
784 The directory where temporary file are stored. The default location
786 is ./var/tmp. The environment variable MYSQL_TMP_DIR will be set to
787 the path for this directory, whether it has the default value or
788 has been set explicitly. This may be referred to in tests.
789 · --user=user_name
791 The MariaDB user name to use when connecting to the server (default
793 root).
794 · --user-args
796 In combination with start* and no test name, drops arguments to
798 mysqld except those specified with --mysqld (if any).
799 · --valgrind[-all]
801 Run mysqltest and mysqld with valgrind. This and the following
803 --valgrind options require that the executables have been built
804 with valgrind support.
805 · --valgrind-mysqld
807 Run the mysqld server with valgrind.
809 · --valgrind-mysqltest
811 Run the mysqltest and mysql_client_test executables with valgrind.
813 · --valgrind-option=str
815 Option to give valgrind. Replaces default option(s). Can be
817 specified more then once&.
818 · --valgrind-path=path
820 Path to the valgrind executable.
822 · --vardir=path
824 Specify the path where files generated during the test run are
826 stored. The default location is ./var. The environment variable
827 MYSQLTEST_VARDIR will be set to the path for this directory,
828 whether it has the default value or has been set explicitly. This
829 may be referred to in tests.
830 · --verbose
832 Give more verbose output regarding test execution. Use the option
834 twice to get even more output. Note that the output generated
835 within each test case is not affected.
836 · --verbose-restart
838 Write when and why servers are restarted between test cases.
840 · --view-protocol
842 Create a view to execute all non updating queries.
844 · --vs-config=config_val
846 Visual Studio configuration used to create executables (default:
848 MTR_VS_CONFIG environment variable) This option is for Windows
849 only.
850 · --wait-all
852 If --start or --start-dirty is used, wait for all servers to exit
854 before termination. Otherwise, it will terminate if one (of
855 several) servers is restarted.
856 · --warnings
858 Search the server log for errors or warning after each test and
860 report any suspicious ones; if any are found, the test will be
861 marked as failed. This is the default behavior, it may be turned
862 off with --nowarnings.
863
866 Copyright © 2007, 2010, Oracle and/or its affiliates, 2010-2015 MariaDB
867 Foundation
868 This documentation is free software; you can redistribute it and/or
870 modify it only under the terms of the GNU General Public License as
871 published by the Free Software Foundation; version 2 of the License.
872 This documentation is distributed in the hope that it will be useful,
874 but WITHOUT ANY WARRANTY; without even the implied warranty of
875 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
876 General Public License for more details.
877 You should have received a copy of the GNU General Public License along
879 with the program; if not, write to the Free Software Foundation, Inc.,
880 51 Franklin Street, Fifth Floor, Boston, MA 02110-1335 USA or see
881 http://www.gnu.org/licenses/.
882
885 For more information, please refer to the MariaDB Knowledge Base,
886 available online at https://mariadb.com/kb/
887
889 MariaDB Foundation (http://www.mariadb.org/).
890 MYSQL-TEST-RUN()