File: show_engine.test

package info (click to toggle)
mariadb-10.5 1%3A10.5.23-0%2Bdeb11u1
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 712,240 kB
  • sloc: ansic: 2,158,658; cpp: 1,843,101; asm: 297,745; perl: 59,967; sh: 53,869; pascal: 38,348; java: 33,919; yacc: 19,639; python: 11,119; xml: 10,126; sql: 10,027; ruby: 8,544; makefile: 6,343; cs: 2,866; lex: 1,205; javascript: 1,037; objc: 80; tcl: 73; awk: 46; 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