mariadb

Tree: 5f4c6942bf

Author	SHA1	Message	Date
Sven Sandberg	09c80e12c5	BUG#49978: Replication tests don't clean up replication state at the end Major replication test framework cleanup. This does the following: - Ensure that all tests clean up the replication state when they finish, by making check-testcase check the output of SHOW SLAVE STATUS. This implies: - Slave must not be running after test finished. This is good because it removes the risk for sporadic errors in subsequent tests when a test forgets to sync correctly. - Slave SQL and IO errors must be cleared when test ends. This is good because we will notice if a test gets an unexpected error in the slave threads near the end. - We no longer have to clean up before a test starts. - Ensure that all tests that wait for an error in one of the slave threads waits for a specific error. It is no longer possible to source wait_for_slave_[sql\|io]_to_stop.inc when there is an error in one of the slave threads. This is good because: - If a test expects an error but there is a bug that causes another error to happen, or if it stops the slave thread without an error, then we will notice. - When developing tests, wait_for_*_to_[start\|stop].inc will fail immediately if there is an error in the relevant slave thread. Before this patch, we had to wait for the timeout. - Remove duplicated and repeated code for setting up unusual replication topologies. Now, there is a single file that is capable of setting up arbitrary topologies (include/rpl_init.inc, but include/master-slave.inc is still available for the most common topology). Tests can now end with include/rpl_end.inc, which will clean up correctly no matter what topology is used. The topology can be changed with include/rpl_change_topology.inc. - Improved debug information when tests fail. This includes: - debug info is printed on all servers configured by include/rpl_init.inc - User can set $rpl_debug=1, which makes auxiliary replication files print relevant debug info. - Improved documentation for all auxiliary replication files. Now they describe purpose, usage, parameters, and side effects. - Many small code cleanups: - Made have_innodb.inc output a sensible error message. - Moved contents of rpl000017-slave.sh into rpl000017.test - Added mysqltest variables that expose the current state of disable_warnings/enable_warnings and friends. - Too many to list here: see per-file comments for details.	15 years ago
	cc05440836	Bug #49741 test files contain explicit references to bin/relay-log positions Some of the test cases reference to binlog position and these position numbers are written into result explicitly. It is difficult to maintain if log event format changes. There are a couple of cases explicit position number appears, we handle them in different ways A. 'CHANGE MASTER ...' with MASTER_LOG_POS or/and RELAY_LOG_POS options Use --replace_result to mask them. B. 'SHOW BINLOG EVENT ...' Replaced by show_binlog_events.inc or wait_for_binlog_event.inc. show_binlog_events.inc file's function is enhanced by given $binlog_file and $binlog_limit. C. 'SHOW SLAVE STATUS', 'show_slave_status.inc' and 'show_slave_status2.inc' For the test cases just care a few items in the result of 'SHOW SLAVE STATUS', only the items related to each test case are showed. 'show_slave_status.inc' is rebuild, only the given items in $status_items will be showed. 'check_slave_is_running.inc' and 'check_slave_no_error.inc' and 'check_slave_param.inc' are auxiliary files helping to show running status and error information easily.	16 years ago
Alfranio Correia	60d4662496	WL#2687 WL#5072 BUG#40278 BUG#47175 Non-transactional updates that take place inside a transaction present problems for logging because they are visible to other clients before the transaction is committed, and they are not rolled back even if the transaction is rolled back. It is not always possible to log correctly in statement format when both transactional and non-transactional tables are used in the same transaction. In the current patch, we ensure that such scenario is completely safe under the ROW and MIXED modes.	16 years ago
Andrei Elkin	c03549bf05	WL#342 heartbeat backporting from 6.0 code base to 5.1.	16 years ago
Serge Kozlov	01e368d1f6	Post-merge patch for extra/rpl_test/rpl_log.test: Remove size of binlog file from SHOW BINARY LOGS. Changing size of binlog file is an affect of adding or removing events to/from binlog and it can be checked in next command of test: SHOW BINLOG EVENTS. For SHOW BINARY LOGS statement enough to show the list of file names.	17 years ago
Mats Kindahl	450cc26b47	Post-merge fixes to fix test cases.	17 years ago
Mats Kindahl	c8574b77d7	Post-merge fixes.	17 years ago
Sven Sandberg	78c8bfdddf	BUG#37975: wait_for_slave_* should increase the timeout Problem 1: tests often fail in pushbuild with a timeout when waiting for the slave to start/stop/receive error. Fix 1: Updated the wait_for_slave_* macros in the following way: - The timeout is increased by a factor ten - Refactored the macros so that wait_for_slave_param does the work for the other macros. Problem 2: Tests are often incorrectly written, lacking a source include/wait_for_slave_to_[start\|stop].inc. Fix 2: Improved the chance to get it right by adding include/start_slave.inc and include/stop_slave.inc, and updated tests to use these. Problem 3: The the built-in test language command wait_for_slave_to_stop is a misnomer (does not wait for the slave io thread) and does not give as much debug info in case of failure as the otherwise equivalent macro source include/wait_for_slave_sql_to_stop.inc Fix 3: Replaced all calls to the built-in command by a call to the macro. Problem 4: Some, but not all, of the wait_for_slave_* macros had an implicit connection slave. This made some tests confusing to read, and made it more difficult to use the macro in circular replication scenarios, where the connection named master needs to wait. Fix 4: Removed the implicit connection slave from all wait_for_slave_* macros, and updated tests to use an explicit connection slave where necessary. Problem 5: The macros wait_slave_status.inc and wait_show_pattern.inc were unused. Moreover, using them is difficult and error-prone. Fix 5: remove these macros. Problem 6: log_bin_trust_function_creators_basic failed when running tests because it assumed @@global.log_bin_trust_function_creators=1, and some tests modified this variable without resetting it to its original value. Fix 6: All tests that use this variable have been updated so that they reset the value at end of test.	18 years ago
mkindahl@dl145h.mysql.com	c5fefc688c	Post-merge fixes.	18 years ago
msvensson@pilot.mysql.com	d930e9bb22	Update path to the load_file	18 years ago
msvensson@pilot.mysql.com	d918988baa	WL#4189 - dynamic configuration support - safe process - cleanups - create new suite for fedarated	18 years ago
cbell/Chuck@mysql_cab_desk.	17c2da8c2b	WL#3228 (NDB) : RBR using different table defs on slave/master This patch adds the ability to store extra field metadata in the table map event. This data can include pack_length() or field_lenght() for fields such as CHAR or VARCHAR enabling developers to add code that can check for compatibilty between master and slave columns. More importantly, the extra field metadata can be used to store data from the master correctly should a VARCHAR field on the master be <= 255 bytes while the same field on the slave is > 255 bytes. ' The patch also includes the needed changes to unpack to ensure that data which is smaller on the master can be unpacked correctly on the slave.	19 years ago
cbell/Chuck@mysql_cab_desk.	74e4da489e	WL#3228 (NDB) : RBR using different table defs on slave/master This patch adds the ability to store extra field metadata in the table map event. This data can include pack_length() or field_lenght() for fields such as CHAR or VARCHAR enabling developers to add code that can check for compatibilty between master and slave columns. More importantly, the extra field metadata can be used to store data from the master correctly should a VARCHAR field on the master be <= 255 bytes while the same field on the slave is > 255 bytes. ' The patch also includes the needed changes to unpack to ensure that data which is smaller on the master can be unpacked correctly on the slave.	19 years ago
Justin.He/justin.he@dev3-240.dev.cn.tlan	da9fdd996b	Bug#19259 rpl_ndb_dd_partitions failed on Solaris Actually, this testcase will fail generally on all testing platforms. The bugs come from the inconsistent bitmap between rpl master and slave. In log_event.cc, the n_bits of m_cols and m_cols_ai are intialized with octal-ceiling m_width, in fact, their n_bits should be equal to m_width. Wrong n_bits will cause bitmap_bits_set() get incorrect value in unpack_row() in rpl_record.cc, then an assertion in unpack_row() will fail and crash sql thread. DBUG_ASSERT(null_ptr == row_data + master_null_byte_count); Meanwhile, because of binlog_prepare_pending_rows_event() changed with correct m_cols, some results of specific testcases should be updated: binlog_multi_engine.test ndb_binlog_multi.test rpl_ndb_dd_partitions.test rpl_ndb_log.test rpl_truncate_7ndb.test rpl_truncate_7ndb_2.test In addition, to ensure rows replication correct between master and slave after the patch, two 'select * from t1' are added in extra/rpl_tests/rpl_log.test, and some testcases include rpl_log.test, therefore, the results of these testcases should be updated likewise: rpl_stm_log.test rpl_row_log.test rpl_ndb_log.test rpl_row_log_innodb.test Totally, results of nine testcases are updated.	19 years ago
tomas@whalegate.ndb.mysql.com	1c15d3e1a1	fixes Bug #25305 (and several other similar test tailures with the same symptom) - make tests wait until ndb connects properly	19 years ago
mats@kindahl-laptop.dnsalias.net	7bc43ebfc9	BUG#24954 (Last_errno and Last_error not set after master_retry_count has been reached): Post-merge patch to handle all the changes to the tree since the tree was cloned.	19 years ago
mats@romeo.(none)	82c71a60f7	- Fixing binary log positions - Eliminating some compiler warnings	19 years ago
mats@romeo.(none)	7c187c2c9b	WL#3464: Add replication event to denote gap in replication Adding an event that can be used to denote that an incident occured on the master. The event can be used to denote a gap in the replication stream, but can also be used to denote other incidents. In addition, the injector interface is extended with functions to generate an incident event. The function will also rotate the binary log after generating an incident event to get a fresh binary log.	19 years ago
msvensson@pilot.blaudden	4367b151c2	Switch back to master before cleanup of the created tables That causes test case for bug#6880 to be run on the master instead of the slave and thus the result files need to be updated	19 years ago
mats@romeo.(none)	e61a1841a5	BUG#22583 (RBR between MyISAM and non-MyISAM tables containing BIT field does not work): Changing packed row format to only include null bits for those columns that are present in the row as well as writing BIT columns in a storage engine-independent format. The change in row format is incompatible with the previous format and a slave will not be able to read the new events.	19 years ago
monty@mysql.com	bb02e07777	Change table_id's to # to make tests portable	20 years ago
ramil@mysql.com	db2acfc926	Fix for bug #20601 : rpl_ndb_log.test failure	20 years ago
evgen@moonbone.local	c0850425e5	rpl_log.test, rpl_stm_log.result: Fixed failing test case field.cc, item_cmpfunc.cc, select.result: After merge fix	20 years ago
msvensson@shellback.(none)	3970e560a6	Cleanup testcases - Add missing drop(s) - Reset changed variables NOTE! These kind of problems are easily found with --check-testcases options to mysql-test-run.pl	20 years ago
jmiller@mysql.com	d022cacbc1	Updated to fix bug in AIX	20 years ago
jmiller@mysql.com	46ad615f6e	rpl_log.test: Fix for failure in aix52 failure during push build	20 years ago
jmiller@mysql.com	2ef6dffebf	rpl_log.test: Remove comments not needed	20 years ago
jmiller@mysql.com	0ab18c91f4	rpl_log.test: Correct fix for test bug #19158	20 years ago
elliot@mysql.com	ac6450b858	BUG#19158 Fixing rpl_row_log_innodb test for pushbuild.	20 years ago
mats@mysql.com	101edab125	WL#3023 (RBR: Use locks in a statement-like manner): Adaptions to make it work with NDB.	20 years ago
jmiller@mysql.com	c63218aa91	Test cleanup	20 years ago
jmiller@mysql.com	23b68e3a5a	More test case updates for using RPL with NDB as default engine	20 years ago
lars@mysql.com	ad126d90e0	WL#1012: All changes as one single changeset. This includes both code and test cases.	20 years ago
jmiller@mysql.com	9f573f0ac8	Adding comment for force manual merge 5.0 -> wl1012	21 years ago
monty@mysql.com	3c12d0ae54	Added end marker for tests to make future merges easier	21 years ago
dlenev@brandersnatch.localdomain	f169114042	WL#874 "Extended LOAD DATA". Now one can use user variables as target for data loaded from file (besides table's columns). Also LOAD DATA got new SET-clause in which one can specify values for table columns as expressions. For example the following is possible: LOAD DATA INFILE 'words.dat' INTO TABLE t1 (a, @b) SET c = @b + 1; This patch also implements new way of replicating LOAD DATA. Now we do it similarly to other queries. We store LOAD DATA query in new Execute_load_query event (which is last in the sequence of events representing LOAD DATA). When we are executing this event we simply rewrite part of query which holds name of file (we use name of temporary file) and then execute it as usual query. In the beggining of this sequence we use Begin_load_query event which is almost identical to Append_file event	21 years ago
serg@serg.mylan	1034677f94	XA (not completely polished out yet)	21 years ago
ingo@mysql.com	309c7412f6	Fix replace_result of $MASTER_MYPORT instead of literal numbers.	22 years ago
monty@mysql.com	e9315f984d	Changed wellformedlen to well_formed_len Fixed that blobs >16M can be inserted/updated Fixed bug when doing CREATE TEMPORARY TABLE ... LIKE	22 years ago
Sinisa@sinisa.nasamreza.org	5ba24f84e1	rpl_log.result: a result file for a fix for bug #2557 rpl_log.test: A test case for a fix for bug #2557	22 years ago
guilhem@gbichot2	df3b1a54f4	This is the final commit for Worklog tasks: * A more dynamic binlog format which allows small changes (1064) * Log session variables in Query_log_event (1063) It contains a few bugfixes (which I made when running the testsuite). I carefully updated the results of the testsuite (i.e. I checked for every one, if the difference between .reject and .result could be explained). Apparently mysql-test-run --manager is broken in 4.1 and 5.0 currently, so I could neither run the few tests which require --manager, nor check that they pass nor modify their .result. But for builds, we don't run with --manager. Apart from --manager, the full testsuite passes, with Valgrind too (no errors). I'm going to push in the next minutes. Remains: update the manual. Note: by chance I saw that (in 4.1, in 5.0) rpl_get_lock fails when run alone; this is normal at it makes assumptions on thread ids. I will fix this one day in 4.1.	22 years ago
guilhem@gbichot2	d6d6c5e1bb	Don't show Slave_IO_State in the testsuite (replace it with #) because it can't be predicted. I manually edited rpl_openssl.result because the test is skipped on my machine. Hope it's correct.	23 years ago
guilhem@gbichot2	c0075fa64b	Final push for WL#1098: "Add a column "Timestamp_of_last_master_event_executed" in SHOW SLAVE STATUS". Finally this is adding - Slave_IO_State (a copy of the State column of SHOW PROCESSLIST for the I/O thread, so that the users, most of the time, has enough info with only SHOW SLAVE STATUS). - Seconds_behind_master. When the slave connects to the master it does SELECT UNIX_TIMESTAMP() on the master, computes the absolute difference between the master's and the slave's clock. It records the timestamp of the last event executed by the SQL thread, and does a small computation to find the number of seconds by which the slave is late.	23 years ago
guilhem@mysql.com	ec280a51ca	Result updates after Dmitri's and my changes to logging with --log-slave-updates. Since my changes, rpl_log.test, whose result file depends on file_id, became non-repeatable, i.e. file_id on slave in SHOW BINLOG EVENTS changed depending on the order of tests (sometimes 1, sometimes 5). Which is logical: as now the slave does not copy Create_file and Exec_load from the relay log (i.e from the master's binlog) to the slave's binlog, but instead lets mysql_load() do the logging, the file_id is now the one whic was used on the slave. Before it was the one which was used on the master, and by chance the master was always restarted for this test because there's a -master.opt file, so file_id on the master is always 1. But now file_id is from the slave so we need to restart the slave. That's why I add an (empty) -slave.opt file. I could have used 'server_stop/start slave', but this would have required the manager, so most of the time mysql-test-run silently skip the test which makes it useless. And I want this test to be run !	23 years ago
monty@mashka.mysql.fi	2fb441fdf7	Remove wrong bug fix when calling create_sort_index. Fix possible replication bug with LOAD DATA ... IGNORE LINES #	23 years ago
monty@narttu.mysql.fi	f5bb1e0907	After merge fix	23 years ago
guilhem@mysql.com	9864ac66c6	A trick (a useless update) to force the slave to wait for TWO rotate events before stopping. This is to make the test's result predictable (depending on the machine the results could formerly be slightly different, though everything is sane in the code; it's not a bug).	23 years ago
guilhem@mysql.com	e91a9c79ba	Test's result update because std_data/words.dat has been lengthened by 500 bytes. Increased some tests' robustness a bit : - Added RESET MASTER to all tests who do SHOW BINLOG EVENTS, to make them independent from previous tests. - Added save_master_pos to these tests to wait for the slave to start before purging its binary logs.	23 years ago
nick@mysql.com	4b7897fc76	Changed binlog name padding from binlog.001 to binlog.000001	23 years ago
nick@mysql.com	59c72048fb	changed syntax from SHOW MASTER LOGS to SHOW BINARY LOGS	23 years ago

41 Commits (5f4c6942bfc6b88a8e934decfcf2f991bce6628e)