1berry/MariaDB-server
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Test is very resource intensive under debug and valgrind runs.

Browse Source 
Under a debug run, the trace file grows to a few gigabytes.
Under valgrind, takes more then 20 minutes due to the high
number of insert statements.
This commit is contained in:
Davi Arnaut 2009-06-08 12:51:06 -03:00
parent 02a5dd38f3
commit 8209a09ef6
1 changed files with 17 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
mysql-test/t/multi_update2.test
View File

@ -2,14 +2,27 @@
# Test of update statement that uses many tables. # Test of update statement that uses many tables.
# #
#
# If we are running with
# - Valgrind -> $VALGRIND_TEST <> 0
# - debug tracing -> @@debug LIKE '%trace%'
# the resource consumtion (storage space needed, runtime) will be extreme.
# Therefore we require that option "big" is set.
#
if (`SELECT ($VALGRIND_TEST <> 0 OR @@debug LIKE '%trace%') AND '$BIG_TEST' = ''`)
{
--skip Need "big" when running with Valgrind or debug
}
#
# Bug#1820 Rows not deleted from second table on multi-table delete
#
--disable_warnings --disable_warnings
DROP TABLE IF EXISTS t1,t2; DROP TABLE IF EXISTS t1,t2;
--enable_warnings --enable_warnings
#
# Bug#1820 Rows not deleted from second table on multi-table delete
#
CREATE TABLE t1 ( a INT NOT NULL, b INT NOT NULL) ; CREATE TABLE t1 ( a INT NOT NULL, b INT NOT NULL) ;
--echo # The protocolling of many inserts into t1 is suppressed. --echo # The protocolling of many inserts into t1 is suppressed.
--disable_query_log --disable_query_log