File: show_engine.test

package info (click to toggle)
mariadb-10.1 10.1.45-0%2Bdeb9u1
  • links: PTS, VCS
  • area: main
  • in suites: stretch
  • size: 476,916 kB
  • sloc: cpp: 1,124,656; ansic: 871,843; perl: 52,917; sh: 40,078; pascal: 35,370; javascript: 15,555; yacc: 14,728; ruby: 8,684; xml: 5,377; sql: 3,490; makefile: 2,934; python: 1,970; java: 1,691; asm: 837; lex: 757; php: 22; sed: 16
file content (31 lines) | stat: -rw-r--r-- 986 bytes parent folder | download | duplicates (11)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
#
# SHOW ENGINE STATUS command
#
# The result might be empty, in which case the test will require rdiff,
# as it is optimistically expects some output from the command
#

--source have_engine.inc

--echo # For most engines SHOW ENGINE .. STATUS produces an empty result,
--echo # so the default result file is empty; but returning a value here is not an error.
--echo # The Status column is masked, because it is likely to contain some
--echo # volatile data (timestamps, memory info, etc.)

--source mask_engine.inc
--replace_column 3 '### Engine status, can be long and changeable ###'
eval
SHOW ENGINE $storage_engine STATUS;

--echo # For SHOW MUTEX even the number of lines is volatile, so the result logging is disabled,
--echo # the test only checks that the command does not produce any errors
--disable_result_log
--source mask_engine.inc
eval
SHOW ENGINE $storage_engine MUTEX;
--source mask_engine.inc
SHOW ENGINE ALL MUTEX;
--enable_result_log

--source cleanup_engine.inc