mariadb

Tree: 4da0c708b5

Author	SHA1	Message	Date
Magnus Svensson	3dbc5cf418	WL#4189 mtr.pl v2 - Pass verbose flag to My::SafeProcess also when starting check_warnings and run_on_all	17 years ago
Joerg Bruehe	3e625f987b	Backport of a fix done by Kent for bug#42278 into the 5.0.72sp1 branch. Original changeset (in the main 5.0 branch): > committer: Kent Boortz <kent@kent-amd64> > branch nick: mysql-5.0-build-bug42278 > timestamp: Fri 2009-01-23 02:59:03 +0100 scripts/make_binary_distribution.sh: From 5.0.48 the NDB client libraries has been missing in the cluster packages, this is now corrected (Bug#42278)	17 years ago
Chad MILLER	d81f6d6104	Merge from team tree.	17 years ago
Chad MILLER	94a080352a	Merge from 5.1 team tree.	17 years ago
Luis Soares	47e19cf2d5	merge: 5.1-rpl (with merge from main) -> 5.1-rpl	17 years ago
Magnus Svensson	0618b83622	WL#4189 mtr.pl v2 - Suppress intentional safemalloc dump warnings - add fflush(stdout) to make sure that the "End safemalloc memory dump." marker is flushed.	17 years ago
Horst Hunger	2255610125	Modified fix for bug#36876 due to reviews: See bug report.	17 years ago
Chad MILLER	34dabc062f	Merge fix for bug 38145 from 5.0.	17 years ago
Andrei Elkin	b33437f18a	Bug #31240 load data infile replication between (4.0 or 4.1) and 5.1 fails Overriding a default value of --secure-file-priv on pb.mtr to be $MYSQLTEST_VARDIR which makes pb's mtr happy to execute the regression test for the bug. mysql-test/suite/rpl/t/rpl_cross_version-master.opt: satisfying pb's mtr that uses --vardir to shm.	17 years ago
Andrei Elkin	5f7750ce6a	Bug #31240 load data infile replication between (4.0 or 4.1) and 5.1 fails Overriding a default value of --secure-file-priv on pb.mtr with a value allowable the test to pass on pb. mysql-test/suite/rpl/t/rpl_cross_version-master.opt: Overriding a default value of --secure-file-priv with a value allowable the test to pass on pb.	17 years ago
Magnus Svensson	2bea349bec	WL#4189 mtr.pl v2 - rewrite "check warnings" to be faster by not creating a full join between error_log and suspicious_patterns while running REGEXP. Instead add a column to error_log that will be set to 1 to indicate a warning and run the 6 REGEXP's we have for suspicious lines as 6 separate full table scans. - Remove the "suspicious_patterns" table from mtr db - Use 'xykls37' as separator when loading the error log, that line should hopefully never exist in a line that should be a warning	17 years ago
Ramil Kalimullin	80fe6268f7	Fix for bug #37756 : enabling fulltext indexes with myisam_repair_threads > 1 causes crash Problem: parallel repair (myisam_repair_threads > 1) of a myisam table with two or more fulltext keys that use the same parser may lead to a server crash. ALTER TABLE ENABLE KEYS is affected as well. Fix: properly initialize fulltext structures for parallel repair. Note: 1. there's no deterministic test case. 2. now we call parser->init() for each fulltext key (not for each fulltext parser used). storage/myisam/ft_parser.c: Fix for bug #37756: enabling fulltext indexes with myisam_repair_threads > 1 causes crash In ftparser_call_initializer() we "group" parsers and allocate parameters for each unique parser used. In case of parallel repairing we may have a bunch of parsers that use the only MI_INFO structure. Each of these parsers must have its own parameter structure in order not to interfere with others. Moreover, the allocation is done without mutex lock so parallel ftparser_call_initializer() calls are unsafe. Now we don't "group" the fulltext parsers. Parameter allocation code moved to ftparser_alloc_param() function which is called from mi_repair_parallel() as well to allocate parameters for each parser used. storage/myisam/ftdefs.h: Fix for bug #37756: enabling fulltext indexes with myisam_repair_threads > 1 causes crash ftparser_alloc_param(MI_INFO *info) added. storage/myisam/mi_check.c: Fix for bug #37756: enabling fulltext indexes with myisam_repair_threads > 1 causes crash ftparser_alloc_param(info) called in case of parallel repair to allocate fulltext parser parameters. storage/myisam/mi_open.c: Fix for bug #37756: enabling fulltext indexes with myisam_repair_threads > 1 causes crash set keyinfo->ftkey_nr and share->ftkeys.	17 years ago
Magnus Svensson	ccca3dfa4e	mtr.pl - default parallel to 1(again)	17 years ago
Magnus Svensson	361a533069	WL#4189 mtr.pl v2 - turn auto detection of parallelism value ON again	17 years ago
Magnus Svensson	2a89260d31	Bug#42320 Read also "mysql.err-old" when checking the server for warnings - disable check of .err-old until bug has been fixed	17 years ago
Magnus Svensson	66f000c912	WL#4198 mtr.pl v2 - fix typo, use "$old_log_error" as name when loading from .err-old file	17 years ago
Magnus Svensson	66bf048dd3	mtr.pl v2 - extend debug prints for "permission denied"	17 years ago
Gleb Shchepa	add8e4d159	Bug #42188 : After-push test file update (see bug 42321)	17 years ago
Magnus Svensson	bbdd0576ee	WL#4189 mtr.pl v2 - Clear test variables "comment" and "logfile" to make sure thay aren't already set from previous run of same test - Print warning if test result already set and set it anyway	17 years ago
Magnus Svensson	0cb63777a7	WL#4189 mtr.pl v2 - fix typo	17 years ago
Magnus Svensson	dc00994962	Merge	17 years ago
Magnus Svensson	7b93194c47	WL#4189 mtr.pl v2 - Don't save ndb_*_fs directory after test failure	17 years ago
Magnus Svensson	a3185ce723	mtr.pl v2 - Add name of error log file to the erro log table to get better erorr message when warning is found	17 years ago
Magnus Svensson	f4ea7624ae	Remove debug printouts of all remaining tests when test suite has been terminated in the middle	17 years ago
Magnus Svensson	0226941c09	mtr.pl v2 - Add debug prints for analyzing mkdir "Permission denied" failure	17 years ago
Magnus Svensson	a7e67cba9a	WL#4189 mtr.pl v2 - Rewrite "check testcase" to use LOAD DATA INFILE instead of 'load_file' in order to speed up the reading of the servers error log. mysql-test/include/check-warnings.test: Use LOAD DATA to load the servers error log into error_log table and then call 'check_warning' stored procedure to filter out any unexpected warnings	17 years ago
Horst Hunger	02c57a12f3	due to merge	17 years ago
Horst Hunger	2775f86773	due to merge.	17 years ago
Gleb Shchepa	93991b6be9	Bug#42188: crash and/or memory corruption with user variables in trigger Interchangeable calls to the mysql_change_user client function and invocations of a trigger changing some user variable caused a memory corruption and a crash. The mysql_change_user API call forces TDH::cleanup() on a server that frees user variable entries. However it didn't reset Item_func_set_user_var::entry to NULL because Item_func_set_user_var::cleanup() was not overloaded. So, Item_func_set_user_var::entry held a pointer to freed memory, that caused a crash. The Item_func_set_user_var::cleanup method has been overloaded to cleanup the Item_func_set_user_var::entry field. mysql-test/r/user_var.result: Added test case for bug #42188. mysql-test/t/user_var.test: Added test case for bug #42188. sql/item_func.cc: Bug#42188: crash and/or memory corruption with user variables in trigger The Item_func_set_user_var::cleanup method has been overloaded to cleanup the Item_func_set_user_var::entry field. sql/item_func.h: Bug#42188: crash and/or memory corruption with user variables in trigger The Item_func_set_user_var::cleanup method has been overloaded to cleanup the Item_func_set_user_var::entry field.	17 years ago
Horst Hunger	d574142888	Fix for bug#39108: Set global wait timeout within the test, not more via opt file. Deleted the opt file. Replaced the sleeps by wait condition. Made some beautyfications. Inserted review results.	17 years ago
Andrei Elkin	db337eb8d8	Bug #31240 load data infile replication between (4.0 or 4.1) and 5.1 fails an additional changeset to remove printing a path name. mysql-test/suite/rpl/r/rpl_cross_version.result: removing a local exec env dependency mysql-test/suite/rpl/t/rpl_cross_version.test: refining a test to not have local exec env dependency.	17 years ago
Andrei Elkin	00ca9099e6	merge from 5.1-bt to a local tree.	17 years ago
Luis Soares	df8543868d	merge: 5.1 -> 5.1-rpl conflicts: Text conflict in client/mysqltest.cc Text conflict in mysql-test/include/wait_until_connected_again.inc Text conflict in mysql-test/lib/mtr_report.pm Text conflict in mysql-test/mysql-test-run.pl Text conflict in mysql-test/r/events_bugs.result Text conflict in mysql-test/r/log_state.result Text conflict in mysql-test/r/myisam_data_pointer_size_func.result Text conflict in mysql-test/r/mysqlcheck.result Text conflict in mysql-test/r/query_cache.result Text conflict in mysql-test/r/status.result Text conflict in mysql-test/suite/binlog/r/binlog_index.result Text conflict in mysql-test/suite/binlog/r/binlog_innodb.result Text conflict in mysql-test/suite/rpl/r/rpl_packet.result Text conflict in mysql-test/suite/rpl/t/rpl_packet.test Text conflict in mysql-test/t/disabled.def Text conflict in mysql-test/t/events_bugs.test Text conflict in mysql-test/t/log_state.test Text conflict in mysql-test/t/myisam_data_pointer_size_func.test Text conflict in mysql-test/t/mysqlcheck.test Text conflict in mysql-test/t/query_cache.test Text conflict in mysql-test/t/rpl_init_slave_func.test Text conflict in mysql-test/t/status.test	17 years ago
Kent Boortz	e610f61d0e	From 5.0.48 the NDB client libraries has been missing in the cluster packages, this is now corrected (Bug#42278)	17 years ago
Andrei Elkin	8c3389f386	Bug #31240 load data infile replication between (4.0 or 4.1) and 5.1 fails It's a regression issue. The reason of the bug appeared to be an error introduced into 5.1 source code. A piece of code in Create_file_log_event::do_apply_event() did not have test coverage which made make test and pb unaware. Fixed with inverting the old value of the return value from Create_file_log_event::do_apply_event(). The rpl test suite is extended with `rpl_cross_version' the file to hold regression cases similar to the current. mysql-test/suite/rpl/r/rpl_cross_version.result: new results file mysql-test/suite/rpl/t/rpl_cross_version-master.opt: options to the server to be able to start replication to itself mysql-test/suite/rpl/t/rpl_cross_version.test: regression test for bug#31240. sql/log_event.cc: Correcting the return value from Create_file_log_event::do_apply_event()	17 years ago
Luis Soares	727707ac52	BUG#40143 federated.federated_server fails sporadically in pushbuild The original goal of the test, as reported on BUG #25721, is to check whether a deadlock happens or not when concurrently CREATING/ALTERING/DROPPING the same server. For that a procedure (p1) is created that runs the exact same CREATE/ALTER/DROP statements for 10K iterations and two different connections (threads - t1 and t2) call p1 concurrently. At the end of the 10K iterations, the test checks if there was errors while running the loop (SELECT e >0). The problem is that In some cases it may happen that one thread, t1, gets scheduled to execute with just enough time to complete the iteration and never bumps into the other thread t2. Meaning that t1 will never run into an SQL exception. On the other hand, the other thread, t2, may run into t1 and never issue any/part of its own statements because it will throw an SQLEXCEPTION. This is probably the case for failures where only one value differs. Furthermore, there is a third scenario: both threads are scheduled to run interleaved for each iteration (or even one thread completes all iterations before the other starts). In this case, both will succeed without any error. This is probably the case for the failure that reports two different values. This patch addresses the failure in pushbuild by removing the error counting and the printout (SELECT > 0) at the end of the test. A timeout should occur if the error that the test is checking surfaces.	17 years ago
Satya B	2e3422fa71	updating to the latest bugteam-5.1 branch	17 years ago
Davi Arnaut	6157433b2a	Merge test case of Bug#40264 to mysql-5.1-bugteam sql/sql_cache.cc: Assert that results are always complete.	17 years ago
Davi Arnaut	ecfdc3560c	Bug#40264: Aborted cached query causes query to hang indefinitely on next cache hit The problem is that the query cache was storing partial results if the statement failed when sending the results to the client. This could cause clients to hang when trying to read the results from the cache as they would, for example, wait indefinitely for a eof packet that wasn't saved. The solution is to always discard the caching of a query that failed to send its results to the associated client. mysql-test/r/query_cache_notembedded.result: Add test case result for Bug#40264 mysql-test/t/query_cache_notembedded.test: Add test case for Bug#40264 sql/sql_cache.cc: Abort if a unreported error was raised.	17 years ago
Horst Hunger	88a36a2157	Changes to WL#4681 to merge to 5.1-main tree.	17 years ago
Satya B	4a3e9851cf	TestCase for BUG#41574 - REPAIR TABLE: crashes for compressed tables Extending the existing testcase written for BUG#40949 to verify repair table operation for compressed tables mysql-test/r/myisampack.result: Modified result file for myisampack.test mysql-test/t/myisampack.test: Modified Testcase to test repair operation for compressed tables	17 years ago
Magnus Svensson	c2a4f3901b	Bug#35735 mysql-test-run.pl creates tmpdir for socket path longer than 70 - Additional patch with improved protection by putting it all inside an "eval" - Calling 'hostpath' on a truncated socket may also croak. - Remove the need to create any directory parts of "path" inside the function.	17 years ago
Serge Kozlov	4562b69fed	Bug#30128: The reason that sometimes events were executed because without STARTS clause server fires immediately after creating event and time between create and delete event sometimes is enough for firing. So adding STARTS clause moves first execution in future after drop of event 1. Added STARTS clause for CREATE EVENT. 2. Updated result file.	17 years ago
Magnus Svensson	bf33a3fa89	Merge	17 years ago
He Zhenxing	46d1e28679	Auto merge	17 years ago
He Zhenxing	d7529bf160	Auto merge	17 years ago
Magnus Svensson	9c76ec9323	Bug#39972 mysql-test-run.pl: Confusing error message under special conditions - Fix problem with for example ./mtr --timer, caused by new version of "Getopt::Long" - Evaluating the "$opt" variable as a string, returns the name of the parameter to be modified instead of "Getopt::Long::Callback" which is the class name	17 years ago
He Zhenxing	b7a66485ca	BUG#41653 rpl_innodb_bug30888 fails sporadically on pushbuild: warning in log In mtr.check_warnings, `text` was declares as type text, which is 64K, and when the server log grows larger than this, it would be truncated, and then check_warnings was actually checking the error messages of a previous test and complain warnings. This patch fixed the problem by change the type of `text` to mediumtext, which is 16M. mysql-test/include/mtr_warnings.sql: change the type of `text` to mediumtext	17 years ago
Bjorn Munch	985d7bb81e	merge	17 years ago
Bjorn Munch	089663f9a7	Bug #40399 Please make mtr print stack trace after every failure SIGABRT is sent to relevant processes after a timeout client/mysqltest.cc: Fixed signal handlers to mysqltest actually dumps core mysql-test/lib/My/CoreDump.pm: Added support for dbx mysql-test/lib/My/SafeProcess.pm: Added dump_core to force process to dump core mysql-test/lib/My/SafeProcess/safe_process.cc: Traps SIGABRT and sends this on to child mysql-test/mysql-test-run.pl: When test times out, force core dumps on mysqltest and servers	17 years ago

... 2 3 4 5 6 ...

56342 Commits (4da0c708b51f5b6df3da7ca759ccac3819030f6e) All Branches Search

56342 Commits (4da0c708b51f5b6df3da7ca759ccac3819030f6e)

All Branches