- 15 Jul, 2008 2 commits
-
-
Sven Sandberg authored
This is not a fix to the bug. I'm just pushing a change to the test case that will produce debug info when the test fails next time.
-
Sven Sandberg authored
Post-push fix. The previous patch did 'reset master' at the wrong place.
-
- 14 Jul, 2008 3 commits
-
-
Sven Sandberg authored
Post-push fixes: forgot to commit an updated result file.
-
Sven Sandberg authored
Post-push fixes: I forgot to include the new files start_slave.inc and stop_slave.inc in the previuos push.
-
Sven Sandberg authored
-
- 10 Jul, 2008 2 commits
-
-
Sven Sandberg authored
removing the option files
-
Sven Sandberg authored
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.
-
- 09 Jul, 2008 1 commit
-
-
Mats Kindahl authored
when resetting replication tests. If not, circular replication setups will leave cruft in the slaves binary log.
-
- 08 Jul, 2008 5 commits
-
-
Mats Kindahl authored
-
Mats Kindahl authored
-
Mats Kindahl authored
Bug #37940 rpl_dual_pos_advance fails sporadically on pushbuild,fail wait_for_slave_to_stop Bug #37941 rpl_flushlog_loop fails sporadically on pushbuild Several tests fail when waiting for the slave to stop in what appears to be timeouts caused by a timeout value set to low. This causes false failures when the servers are loaded. In order to try to avoid false negatives, we increase the timeout 10 times and also print some more information in the event that the slave fails to stop when expected to. We add a printout of the current processes running to be able to see if any process have been executing for an unexpectedly long time, and also print the binlog events at the position indicated by SHOW SLAVE STATUS.
-
Sven Sandberg authored
-
Sven Sandberg authored
This is not a fix, it just disables the erroneous test cases.
-
- 07 Jul, 2008 6 commits
-
-
Sven Sandberg authored
-
Sven Sandberg authored
Problem: the test syncs slave by a 'wait_condition' waiting until table t1 has 5000 rows. However, there is no guarantee that t1 makes it to the slave before the wait_condition. Fix: sync_slave_with_master just after t1 was created.
-
Sven Sandberg authored
-
Sven Sandberg authored
-
Sven Sandberg authored
The file tree in mtr's vardir has changed so an old hard-coded path in mysql-test/t/subselect.test didn't work. Fix: update the paths in the test.
-
Sven Sandberg authored
positions changed. Fixed by removing binlog positions from output, and also: - removed code not used to verify the tested property - added comments
-
- 06 Jul, 2008 3 commits
-
-
Sven Sandberg authored
Made the test innodb_max_dirty_pages_pct_func clean up after itself.
-
Sven Sandberg authored
-
Sven Sandberg authored
Problem: rpl_ndb_transaction fails because it assumes nothing is written to the binlog at a certain point. However, ndb may binlog updates in ndb system tables at a nondeterministic time point after an ndb table update has been committed. Fix: break the test into two. rpl_ndb_transaction still does the ndb updates needed by the first half of the test. The new test case rpl_bug26395 includes the part that assumes nothing more will be written to the binlog.
-
- 04 Jul, 2008 1 commit
-
-
Sven Sandberg authored
Problem 1: main.loaddata tried to trigger an error caused by reading files outside the vardir, by reading itself. However, if loaddata.test is not world-readable (e.g., umask=0077), then another error is triggered. Fix 1: allow the other error too. Problem 2: rpl_slave_skip and rpl_innodb_mixed_dml tried to copy a file from mysql-test/suite/rpl/data to mysql-test/var and then read it. That failed too if umask=0077, since the file would not become world-readable. Fix 2: move the files from mysql-test/suite/rpl/data to mysql-test/std_data and update tests accordingly. Remove the directory mysql-test/suite/rpl/data.
-
- 01 Jul, 2008 1 commit
-
-
Matthias Leich authored
-
- 30 Jun, 2008 2 commits
-
-
Matthias Leich authored
Bug#36787 Test funcs_1.charset_collation_1 failing Details: 1. Skip charset_collation_1 if charset "ucs2_bin" is missing (property which distincts "vanilla" builds from the others) 2. Let builds with version_comment LIKE "%Advanced%" (found them for 5.1) execute charset_collation_3. 3. Update comments charset_collation.inc so that they reflect the current experiences.
-
Joerg Bruehe authored
-
- 25 Jun, 2008 3 commits
-
-
Matthias Leich authored
-
Matthias Leich authored
Bug#37492 timing bug in subselect.test + similar weaknesses found during testing + replace error numbers by error names
-
Gleb Shchepa authored
-
- 24 Jun, 2008 4 commits
-
-
Gleb Shchepa authored
-
Gleb Shchepa authored
Bug#35480: BOM detection code crashes mysql CLI with zero-sized input MySQL client crashed if no input was passed to it.
-
Gleb Shchepa authored
Bug#33812: mysql client incorrectly parsing DELIMITER Remove unnecessary and incorrect code that tried to pull delimiter commands out of the middle of statements.
-
Gleb Shchepa authored
as a commentary mysql client has been modified to interpret EOL after standalone -- commentary strings like whitespace character (according to http://dev.mysql.com/doc/refman/5.0/en/ansi-diff-comments.html)
-
- 21 Jun, 2008 1 commit
-
-
Tatiana A. Nurnberg authored
-
- 20 Jun, 2008 5 commits
-
-
Joerg Bruehe authored
-
Tatiana A. Nurnberg authored
Remove unnecessary and incorrect code that tried to pull delimiter commands out of the middle of statements.
-
Matthias Leich mleich@mysql.com authored
-
Joerg Bruehe authored
-
Andrei Elkin authored
-
- 19 Jun, 2008 1 commit
-
-
Andrei Elkin authored
The crash appeared to be a result of allocating an instance of Discrete_interval automatically that that was referred in out-of-declaration scope. Fixed with correcting backing up and restoring scheme of auto_inc_intervals_forced, introduced by bug#33029, by means of shallow copying; added simulation code that forces executing those fixes of the former bug that targeted at master-and-slave having incompatible bug#33029-prone versions.
-