An error occurred fetching the project authors.
- 30 Dec, 2010 1 commit
-
-
Dmitry Shulga authored
-
- 20 Dec, 2010 1 commit
-
-
Anitha Gopi authored
Bug #59055 : Remove ndb tests from repository. Removal of tests from sys_vars is pending. It has some issues that are yet to be resolved
-
- 24 Nov, 2010 2 commits
-
-
Alexander Nozdrin authored
- Mark main.gis experimental
-
Alexander Nozdrin authored
-
- 07 Nov, 2010 1 commit
-
-
He Zhenxing authored
-
- 01 Nov, 2010 1 commit
-
- 27 Oct, 2010 1 commit
-
-
Anitha Gopi authored
-
- 07 Oct, 2010 1 commit
-
-
Dmitry Shulga authored
set to 128k.
-
- 06 Oct, 2010 1 commit
-
-
Luis Soares authored
x86_64 debug_max Removed test cases affected by this bug from experimental list.
-
- 24 Sep, 2010 1 commit
-
-
Mattias Jonsson authored
Update to previous patch according to reviewers comments. Removing parts.partition_alter4_innodb from default.experimental (Also closed bug#45299 as a duplicate of bug#56659 as a result of this.) Adding run of tests requiring --big-test flag to default.weekly to keep the coverage.
-
- 07 Sep, 2010 1 commit
-
-
Sergey Vojtovich authored
were marked as experimental due to BUG38965.
-
- 31 Aug, 2010 1 commit
-
-
Alexander Nozdrin authored
-
- 17 Aug, 2010 1 commit
-
-
Vasil Dimov authored
Track this via: Bug#56063 InnoDB Plugin mysql-tests fail on Solaris
-
- 03 Aug, 2010 1 commit
-
-
Georgi Kodinov authored
The enum system variables were handled inconsistently as ints, unsigned int and unsigned long on various places. This caused problems on platforms on which sizeof(int) != sizeof(long). Fixed by homogenizing the type of the enum variables to unsigned int, since it's size compatible with the C enum type. Removed the test from the experimental list.
-
- 26 Jul, 2010 1 commit
-
-
Alexander Nozdrin authored
-
- 28 Jun, 2010 1 commit
-
-
Alexander Nozdrin authored
-
- 26 Jun, 2010 1 commit
-
-
Alexander Nozdrin authored
-
- 15 Jun, 2010 1 commit
-
-
Alexander Nozdrin authored
-
- 03 Jun, 2010 1 commit
-
-
Horst.Hunger authored
-
- 01 Jun, 2010 2 commits
-
-
Georgi Kodinov authored
-
Georgi Kodinov authored
-
- 03 Jun, 2010 1 commit
-
-
Horst.Hunger authored
-
- 11 May, 2010 1 commit
-
-
Alexander Nozdrin authored
-
- 04 May, 2010 1 commit
-
-
Alexander Nozdrin authored
-
- 30 Apr, 2010 1 commit
-
-
Alexander Nozdrin authored
There were two problems here: 1. misleading error message 2. abusing KILL QUERY in the test case 1. The server reported "'DELETE FROM t1' failed: 1689: Wait on a lock was aborted due to a pending exclusive lock", while the proper error message should be "'DELETE FROM t1' failed: 1317: Query execution was interrupted". The problem is that the server has two different flags for signalling that a query is being killed: THD::killed and mysys_var::abort. The test case triggers a race: sometimes mysys_var::abort is set earlier than THD::killed. That leads to the following situation: - thr_lock() checks mysys_var::abort and returns error status, since mysys_var::abort is set; - the caller (mysql_lock_tables()) gets an error from thr_lock(), but THD::killed is not set, so it decides that thr_lock() couldn't get a lock due to a pending exclusive lock. This is a known issue with the server and it's not going to be fixed soon. 5.5 differs from 5.1 here as follows: when thr_lock() returns an error: - 5.1 continues trying thr_lock() until success; - 5.5 propagates the error 2. The test case uses KILL QUERY is a highly concurent environment. The fix is to wait for the dying statement to rest in peace before executing another DELETE FROM t1.
-
- 26 Apr, 2010 1 commit
-
-
Alexander Nozdrin authored
-
- 10 Apr, 2010 1 commit
-
-
Alexander Nozdrin authored
-
- 23 Mar, 2010 1 commit
-
-
Alexey Kopytov authored
as done in 6.0 due to bug #47146.
-
- 22 Mar, 2010 1 commit
-
-
Alexander Nozdrin authored
experimental due to Bug 52202.
-
- 05 Mar, 2010 1 commit
-
-
Alexander Nozdrin authored
-
- 02 Mar, 2010 1 commit
-
-
Alexander Nozdrin authored
-
- 22 Feb, 2010 1 commit
-
-
Alexander Nozdrin authored
The patch is ready and will be pushed via -bugfixing.
-
- 17 Feb, 2010 1 commit
-
-
Magne Mahre authored
This is a post-fix cleanup to move rpl.rpl_timezone out of 'experimental' state.
-
- 01 Feb, 2010 1 commit
-
-
Georgi Kodinov authored
resulution of bug #46895.
-
- 31 Jan, 2010 1 commit
-
-
Alexander Nozdrin authored
-
- 28 Jan, 2010 1 commit
-
-
Alexander Nozdrin authored
- main.outfile_loaddata @solaris due to Bug#46895 - main.signal_demo3 @solaris due to Bug#47791 - main.sp @solaris due to Bug#47791 - rpl.rpl_slave_load_remove_tmpfile @windows due to Bug#50474
-
- 27 Jan, 2010 1 commit
-
-
The 'rpl_get_master_version_and_clock' test verifies if the slave I/O thread tries to reconnect to master when it tries to get the values of the UNIX_TIMESTAMP, SERVER_ID from master under network disconnection. So the master server is restarted for making the transient network disconnection, during the period the COM_REGISTER_SLAVE failures are produced in server log file when the slave I/O thread tries to register on master. To fix the problem, suppress COM_REGISTER_SLAVE failures in server log file by mtr suppression, because they are expected.
-
- 26 Jan, 2010 1 commit
-
-
Luis Soares authored
- rpl.rpl_slave_load_remove_tmpfile - rpl.rpl_sync
-
- 25 Jan, 2010 1 commit
-
-
Alexander Nozdrin authored
-
- 23 Jan, 2010 1 commit
-
-
Marc Alff authored
-