Bug#50057: SHOW PROFILE CPU for Windows
On QA request, adding test that causes new code to be called. Even if we cannot validate the result, this will at least increase the code coverage.
This commit is contained in:
parent
fe6f55d6a2
commit
a5548f3f07
10
mysql-test/r/show_profile.result
Normal file
10
mysql-test/r/show_profile.result
Normal file
@ -0,0 +1,10 @@
|
||||
SET profiling = 1;
|
||||
SELECT 1;
|
||||
1
|
||||
1
|
||||
SHOW PROFILES;
|
||||
Query_ID Duration Query
|
||||
1 # SELECT 1
|
||||
SHOW PROFILE FOR QUERY 1;
|
||||
SHOW PROFILE CPU FOR QUERY 1;
|
||||
SET profiling = 0;
|
18
mysql-test/t/show_profile.test
Normal file
18
mysql-test/t/show_profile.test
Normal file
@ -0,0 +1,18 @@
|
||||
#
|
||||
# Test for show profiles
|
||||
# No meaningful check is possible.
|
||||
# So it only checks that SET profiling is possible and
|
||||
# that SHOW PROFILES, SHOW PROFILE FOR QUERY and SHOW PROFILE CPU FOR QUERY
|
||||
# do not cause syntax errors. It also increases code coverage for sql_profile.cc
|
||||
|
||||
--source include/have_profiling.inc
|
||||
SET profiling = 1;
|
||||
SELECT 1;
|
||||
--replace_column 2 #
|
||||
SHOW PROFILES;
|
||||
--disable_result_log
|
||||
SHOW PROFILE FOR QUERY 1;
|
||||
SHOW PROFILE CPU FOR QUERY 1;
|
||||
--enable_result_log
|
||||
SET profiling = 0;
|
||||
|
Loading…
x
Reference in New Issue
Block a user