mariadb

Tree: 40db2c21e4

Author	SHA1	Message	Date
Magnus Svensson	39ad2dc05a	Bug #38181 Please print more debug info when tests fail	18 years ago
Magnus Svensson	079fa90b8d	Turn off timestamping	18 years ago
msvensson@pilot.(none)	10348f0f38	(temporarily)Turn on timestamp by default	18 years ago
msvensson@pilot.(none)	447916b9e6	Make printout of $name nicer Remove debug printouts	18 years ago
msvensson@pilot.mysql.com	39e11a1ddb	Add printouts	18 years ago
msvensson@pilot.mysql.com	9d6d039cf1	Tune reporting	18 years ago
msvensson@pilot.mysql.com	fb88bd04a6	Set "timediff" to off by default	18 years ago
msvensson@pilot.mysql.com	ec03ad0591	Move opt_timer to mtr_report.pm	18 years ago
msvensson@pilot.mysql.com	b9a810dd25	Correctly calculate failed tests	18 years ago
msvensson@pilot.mysql.com	8c97dc80ca	Print tests that has been run but shouldn't and vice versa Use opt_start_timeout also for ndb Remove the .result files generated by 'check_testcase'	18 years ago
msvensson@pilot.mysql.com	4f9409c835	Move code that saves datadirs to test server Remove mtr_report_test_failed	18 years ago
msvensson@pilot.mysql.com	b18a64979a	Run all check-warning and check-testcase in parallel, this also give the oportunity to check if any other process fails during this. Add possiblitiy to store "user_data" in a Safeprocess Add function to get pid from a SafeProcess	18 years ago
msvensson@pilot.mysql.com	5681c99645	Print name(of thread) also in mtr_report, testserver does not set name so it will still look the same, but makes debugging much easier	18 years ago
msvensson@pilot.mysql.com	7e8898aaca	Replace all - with - in $opt name	18 years ago
msvensson@pilot.mysql.com	ba900fe302	Add support for running in parallel	18 years ago
msvensson@pilot.mysql.com	433c1c3d7b	Check warnings in servers error log as part of test case	18 years ago
msvensson@pilot.mysql.com	201ce48d5d	After merge fixes	18 years ago
msvensson@pilot.mysql.com	06cf8665c5	Fix after merge	18 years ago
msvensson@pilot.mysql.com	86d065f525	Make mtr_report.pl into it's own package Remove mtr_log_*	18 years ago
msvensson@pilot.mysql.com	abb0bdde9e	Add --verbose-restart	18 years ago
mkindahl@dl145h.mysql.com	ff40ccb8d7	Masking out some more errors and warnings that are benign.	18 years ago
mkindahl@dl145h.mysql.com	dc96cb21bf	Removing expected errors from slave from the warnings file.	18 years ago
msvensson@pilot.mysql.com	727afed657	Add --repeat and --retry	18 years ago
msvensson@pilot.mysql.com	9087ee9170	Try to dynamically change option, restart if it fails	18 years ago
kostja@bodhi.(none)	572ab7a6b0	Silence a new warning printed by rpl_row_tabledefs_3innodb test execution.	18 years ago
msvensson@pilot.mysql.com	d918988baa	WL#4189 - dynamic configuration support - safe process - cleanups - create new suite for fedarated	18 years ago
msvensson@pilot.mysql.com	16d372ce7d	Add suppressions for expected warning messages that appears in slave's error log when running rpl_extraColmaster_*.test	18 years ago
msvensson@shellback.(none)	20fe800c45	WL#3949 Test should set binlog format dnamically - Reorganize collect a little to make it easier to apply optimizations and settings to collected test cases. - Add suite/rpl/combination file - Rename include/set_binlog_format_x.inc to .sql since thay are run by "mysql"	18 years ago
kaa@polly.(none)	347c33d606	Fix for bug #32080 : Excessive warnings on Solaris: setrlimit could not change the size of core files. Suppress the 'setrlimit could not change the size of the core files' warning in mysql-test-run. We do not want core files on some of the PushBuild hosts, and PushBuild itself does not set --core-files, so that warning is expected.	18 years ago
tsmith@ramayana.hindu.god	3cfd655143	Minor update to allowed errors list in mysql-test's mtr_report.pl	18 years ago
jani@hynda.mysql.fi	d3a0ce08c7	Fixed a wrong regexp in mysql-test-run.	18 years ago
serg@janus.mylan	5562142950	mtr_report.pl: InnoDB errors are no less important for pushbuild to monitor than InnoDB warnings	18 years ago
cmiller@zippy.cornsilk.net	eedde95a33	Change URLs. Our web server has been restructured several times, and references to it in our source code has stayed the same. This patch from Paul DuBois updates all URLs to modern semantics.	18 years ago
msvensson@shellback.(none)	cc00660f95	WL#3935 Improve mysqltest report and exitcode for diff - Move the code to generate test report to the test tool(in this case mysqltest) where the best control of what failed is - Simplify the code in mysql-test-run.pl - mysqltest will now find what diff to use in a best effort attempt using "diff -u", "diff -c" and finally dumping the two files verbatim in the report.	19 years ago
msvensson@pilot.(none)	ea692e9028	Improve report on test execution time Define tot_real_tim locally in mtr_report.pl	19 years ago
msvensson@shellback.(none)	b3db467178	Send output to var/log/mysql-test-run.log to facilitate easier debugging of mysql-test-run.pl	19 years ago
mats@kindahl-laptop.dnsalias.net	ef36039db6	BUG#29809 (Slave SQL errors in warnings file): Adding code to filter out slave SQL errors since these are checked by the tests themselves.	19 years ago
svoj@mysql.com/june.mysql.com	b94217491a	BUG#29839 - lowercase_table3.test: Cannot find table test/T1 from the internal data dictiona - re-enabled lowercase_table3 test; - added a rule to throw away expected warning to mtr_report.pl; - fixed a test case to produce unique warning.	19 years ago
svoj@mysql.com/june.mysql.com	ee13e03ca0	BUG#29807 - innodb_mysql.test: Cannot find table test/t2 from the internal data dictionary - re-enabled innodb_mysql test; - added a rule to through away expected warning to mtr_report.pl; - fixed a test case to produce unique warning.	19 years ago
anozdrin/alik@ibm.	9fae9ef66f	Patch for the following bugs: - BUG#11986: Stored routines and triggers can fail if the code has a non-ascii symbol - BUG#16291: mysqldump corrupts string-constants with non-ascii-chars - BUG#19443: INFORMATION_SCHEMA does not support charsets properly - BUG#21249: Character set of SP-var can be ignored - BUG#25212: Character set of string constant is ignored (stored routines) - BUG#25221: Character set of string constant is ignored (triggers) There were a few general problems that caused these bugs: 1. Character set information of the original (definition) query for views, triggers, stored routines and events was lost. 2. mysqldump output query in client character set, which can be inappropriate to encode definition-query. 3. INFORMATION_SCHEMA used strings with mixed encodings to display object definition; 1. No query-definition-character set. In order to compile query into execution code, some extra data (such as environment variables or the database character set) is used. The problem here was that this context was not preserved. So, on the next load it can differ from the original one, thus the result will be different. The context contains the following data: - client character set; - connection collation (character set and collation); - collation of the owner database; The fix is to store this context and use it each time we parse (compile) and execute the object (stored routine, trigger, ...). 2. Wrong mysqldump-output. The original query can contain several encodings (by means of character set introducers). The problem here was that we tried to convert original query to the mysqldump-client character set. Moreover, we stored queries in different character sets for different objects (views, for one, used UTF8, triggers used original character set). The solution is - to store definition queries in the original character set; - to change SHOW CREATE statement to output definition query in the binary character set (i.e. without any conversion); - introduce SHOW CREATE TRIGGER statement; - to dump special statements to switch the context to the original one before dumping and restore it afterwards. Note, in order to preserve the database collation at the creation time, additional ALTER DATABASE might be used (to temporary switch the database collation back to the original value). In this case, ALTER DATABASE privilege will be required. This is a backward-incompatible change. 3. INFORMATION_SCHEMA showed non-UTF8 strings The fix is to generate UTF8-query during the parsing, store it in the object and show it in the INFORMATION_SCHEMA. Basically, the idea is to create a copy of the original query convert it to UTF8. Character set introducers are removed and all text literals are converted to UTF8. This UTF8 query is intended to provide user-readable output. It must not be used to recreate the object. Specialized SHOW CREATE statements should be used for this. The reason for this limitation is the following: the original query can contain symbols from several character sets (by means of character set introducers). Example: - original query: CREATE VIEW v1 AS SELECT _cp1251 'Hello' AS c1; - UTF8 query (for INFORMATION_SCHEMA): CREATE VIEW v1 AS SELECT 'Hello' AS c1;	19 years ago
msvensson@pilot.(none)	8661497e9b	WL#3933 Split main test suite to rpl, rpl_ndb and ndb - Update mysql-test-run.pl to collect tests from several suites - Group test into suites - Add suite.opt file	19 years ago
msvensson@pilot.(none)	840344589e	Add name of test that generated the warning to "warnings" file	19 years ago
msvensson@pilot.(none)	4d3f3f676f	Bug#28742 mysql-test-run is very slow on "Stopping All Servers" step - Improve shutdown algorithm - Wait up to 5 seconds for processes to exit after their port is free	19 years ago
bar@mysql.com/bar.myoffice.izhnet.ru	020eedd446	mtr_report.pl: Ignore warning about file name having question marks.	19 years ago
aelkin/elkin@dsl-hkibras1-ff5dc300-70.dhcp.inet.fi	89639e7679	yellow warnings on pb. Setting the plug of a harmless warning.	19 years ago
tsmith@quadxeon.mysql.com	13adcedc90	mtr_report.pl: Add another exception to the acceptable mysqld errors, for test case for bug 28436	19 years ago
jani@a88-113-38-195.elisa-laajakaista.fi	2c8f4f9791	Added casts to avoid compiler warnings and fixed a wrong type. --- Added casts and fixed wrong type. --- Added casts and fixed wrong type. --- Merge jamppa@bk-internal.mysql.com:/home/bk/mysql-5.1-marvel into a88-113-38-195.elisa-laajakaista.fi:/home/my/bk/mysql-5.1-marvel --- Don't give warning that readonly variable is forced to be readonly mysql-test-run run now fails if we have [Warning] and [ERROR] as tags in .err file Fixed wrong reference to the mysql manual Fixed wrong prototype that caused some tests to fail on 64 bit platforms --- Disabled compiler warnings mainly for Win 64. --- Added casts to remove compiler warnings on windows Give warnings also for safe_mutex errors found by test system Added some warnings from different machines in pushbuild --- Merge bk-internal.mysql.com:/home/bk/mysql-5.1-marvel into mysql.com:/home/my/mysql-5.1 --- Added escapes for double quotes and parenthesis. --- Archive db fix plus added non-critical warnings in ignore list. --- Fixed previously added patch and added new ignored warning.	19 years ago
monty@mysql.com/narttu.mysql.fi	0e2767e16b	Added casts to remove compiler warnings on windows Give warnings also for safe_mutex errors found by test system Added some warnings from different machines in pushbuild	19 years ago
monty@mysql.com/narttu.mysql.fi	2d6d45130e	Don't give warning that readonly variable is forced to be readonly mysql-test-run run now fails if we have [Warning] and [ERROR] as tags in .err file Fixed wrong reference to the mysql manual Fixed wrong prototype that caused some tests to fail on 64 bit platforms	19 years ago
thek@adventure.(none)	dec5c2e048	Bug#28644 Memory status report confused with memory leak This patch removes a false memory leak error report from the test suite. There is a test case that puposely provokes a SAFEMALLOC leak report, even though there is no actual leak.	19 years ago

23 Commits (40db2c21e4d21ff2bc83cd556a291ec40fad89a3)