mariadb

Tree: 16fb2963ff

Author	SHA1	Message	Date
Kristian Nielsen	16fb2963ff	Fix typo that breaks compilation on platforms without atomics.	11 years ago
Jan Lindström	76c3981e43	Fix test case to allow success on create table (Windows).	11 years ago
Elena Stepanova	c9a8859db6	MDEV-7255 Failures in engines/* tests	11 years ago
Elena Stepanova	f7fed26390	Storage engines tests: ALTER ONLINE works differently for MERGE in 10.0	11 years ago
Elena Stepanova	010724f6c5	Run engines tests for MyISAM and in-built InnoDB	11 years ago
Jan Lindström	5bba1109b2	Add possibility to success on Windows.	11 years ago
Elena Stepanova	c8f7f98737	MDEV-7255 Failures in engines/* tests, part 6 Updated hardcoded event numbers according to current GTID logic	11 years ago
Elena Stepanova	f02f06172c	MDEV-7255 Failures in engines/* tests, part 5 RENAME TABLE on a non-existing table produces a better error message	11 years ago
Elena Stepanova	d5f52fec77	MDEV-7255 Failures in engines/* tests, part 4 Updated engines/* test results according to the bugfix MDEV-5894 (MySQL BUG#34750: Print database name in Unknown Table error message)	11 years ago
Elena Stepanova	27ac97ef9e	MDEV-7255 Failures in engines/* tests, part 3 Error message was changed along with CREATE OR REPLACE TABLE fixes	11 years ago
Elena Stepanova	aafdc4b16e	MDEV-7255 Failures in engines/* tests, part 2 Result files updated according to bugfix for MySQL#55843 (Handled condition appears as not handled)	11 years ago
Elena Stepanova	cc06415fd6	MDEV-7255 Failures in engines/* tests, part 1 In 10.0 output of SHOW DATABASES appears to be sorted, while in result files it is not. Added sorted_result for certainty and updated result files.	11 years ago
Sergei Golubchik	2b5db1d5bc	put at least some output-generating statement in the test otherwise mysqltest complains "No queries executed but non-empty result file found!"	11 years ago
Sergei Golubchik	b3aed01ae9	fix include/not_embedded.inc to be independent from the environment in particular, not fail with --vertical_results	11 years ago
Kristian Nielsen	5fc2814698	MDEV-7251: Test failure in rpl.rpl_parallel There was a race. The test case was expecting the slave to start processing a particular DELETE statement, then the test would stop the slave at this point. But there was missing something to wait until the slave would actually reach this point; thus depending on timing it was possible that the slave would be stopped too early, causing .result file difference. Fixed by adding an appropriate wait to the test case.	11 years ago
Jan Lindström	6cd78eedea	MDEV-7242: innodb.innodb-mdev7046 fails in various ways on buildbot Problem with test is that test causes OS failures that change. Idea with test is just to test that server does not crash, no other output is necessary.	11 years ago
Kristian Nielsen	d79cce86ab	MDEV-4393: show_explain.test times out randomly The problem was a race between the debug code in the server and the SHOW EXPLAIN FOR in the test case. The test case would wait for a query to reach the first point of interest (inside dbug_serve_apcs()), then send it a SHOW EXPLAIN FOR, then wait for the query to reach the next point of interest. However, the second wait was insufficient. It was possible for the the second wait to complete immediately, causing both the first and the second SHOW EXPLAIN FOR to hit the same invocation of dbug_server_apcs(). Then a later invocation would miss its intended SHOW EXPLAIN FOR and hang, and the test case would eventually time out. Fix is to make sure that the second wait can not trigger during the first invocation of dbug_server_apcs(). We do this by clearing the thd_proc_info (that the wait is looking for) before processing the SHOW EXPLAIN FOR; this way the second wait can not start until the thd_proc_info from the first invocation has been cleared.	11 years ago
Kristian Nielsen	1eed274848	Fix wording in error log message, to be consistent with other messages ("IO thread" -> "I/O thread").	11 years ago
Kristian Nielsen	0450623f73	MDEV-7236: rpl.rpl_gtid_basic failed in buildbot with wait_condition timeout Fix rare failures in test case rpl.rpl_gtid_basic: - Add another possible error code when a connection is killed. - Make sure that the IO thread has had time to complete its stop after START SLAVE UNTIL. Otherwise, START SLAVE might run before IO thread stop, leaving the test case with a stopped IO thread that eventually causes a wait timeout.	11 years ago
Kristian Nielsen	50b42441a6	MDEV-7241: rpl.rpl_parallel2 fails sporadically in buildbot There was a race, a small window between updating slave position and updating Seconds_Behind_Master, during which the test case could see the wrong value. Fix by waiting for the expected status to appear.	11 years ago
Sergei Golubchik	433b28cede	add a proper cleanup to innodb.innodb-mdev7046 test	11 years ago
Sergei Golubchik	ba076763ec	remove ssl debugging report_errors() function that was sometimes destroying the state	11 years ago
Sergei Golubchik	4e9e04b28b	tests that require server restart cannot be run with --embedded	11 years ago
Sergei Golubchik	230132dc41	bump the version	11 years ago
Sergei Golubchik	a4baf9b3ea	test failure: make list_files more selective to prevent db.opt from showing up	11 years ago
Sergei Golubchik	e3108e6d2b	silence stderr correctly	11 years ago
Sergei Golubchik	912bbfda12	MDEV-7144 Warnings "bytes lost" during server shutdown after running connect.part_file test in buildbot	11 years ago
Kristian Nielsen	52b25934d7	MDEV-7237: Parallel replication: incorrect relaylog position after stop/start the slave The replication relay log position was sometimes updated incorrectly at the end of a transaction in parallel replication. This happened because the relay log file name was taken from the current Relay_log_info (SQL driver thread), not the correct value for the transaction in question. The result was that if a transaction was applied while the SQL driver thread was at least one relay log file ahead, _and_ the SQL thread was subsequently stopped before applying any events from the most recent relay log file, then the relay log position would be incorrect - wrong relay log file name. Thus, when the slave was started again, usually a relay log read error would result, or in rare cases, if the position happened to be readable, the slave might even skip arbitrary amounts of events. In GTID mode, the relay log position is reset when both slave threads are restarted, so this bug would only be seen in non-GTID mode, or in GTID mode when only the SQL thread, not the IO thread, was stopped.	11 years ago
Alexander Barkov	f8e1952be4	MDEV-7149 Constant propagation erroneously applied for LIKE Simply disallowing equality propagation into LIKE. A more delicate fix is be possible, but it would need too many changes, which is not desirable in 10.0 at this point.	11 years ago
Kristian Nielsen	74e581b7c4	MDEV-7037: MariaDB 10.0 does not build on Debian / kfreebsd-i386/amd64 due to MTR failure: multi_source.gtid MDEV-7106: Sporadic test failure in multi_source.gtid MDEV-7153: Yet another sporadic failure of multi_source.gtid in buildbot This patch fixes three races in the multi_source.gtid test case that could cause sporadic failures: 1. Do not put SHOW ALL SLAVES STATUS in the output, the output is not stable. 2. Ensure that slave1 has replicated as far as expected, before stopping its connection to master1 (otherwise the following wait will time out due to rows not replicated from master1). 3. Ensure that slave2 has replicated far enough before connecting slave1 to it (otherwise we get an error during connect that slave1 is ahead of slave2).	11 years ago
Alexander Barkov	5ae1639c02	Backporting a cleanup in boolean function from 10.1: Moving Item_bool_func2 and Item_func_opt_neg from Item_int_func to Item_bool_func. Now all functions that return is_bool_func()=true have a common root class Item_bool_func. This change is needed to fix MDEV-7149 properly.	11 years ago
Jan Lindström	e15a83c0c7	Better comments part 2 with proof and simplified implementation. Thanks to Daniel Black.	11 years ago
Jan Lindström	43054872be	MDEV-7214: Test failure in main.partition_innodb Problem is on test it tried to verify that no files were left on test database. Fix: There's no need to list other file types, it can only list *.par files	11 years ago
Kristian Nielsen	06d0d09077	MDEV-6582: DEBUG_SYNC does not reset mysys_var->current_mutex, causes assertion "Trying to unlock mutex that wasn't locked" The bug was in DEBUG_SYNC. When waiting, debug_sync_execute() temporarily sets thd->mysys_var->current_mutex to a new value while waiting. However, if the old value of current_mutex was NULL, it was not restored, current_mutex remained set to the temporary value (debug_sync_global.ds_mutex). This made possible the following race: Thread T1 goes to KILL thread T2. In THD::awake(), T1 loads T2->mysys_var->current_mutex, it is set to ds_mutex, T1 locks this mutex. Now T2 runs, it does ENTER_COND, it sets T2->mysys_var->current_mutex to LOCK_wait_commit (for example). Then T1 resumes, it reloads mysys_var->current_mutex, now it is set to LOCK_wait_commit, T1 unlocks this mutex instead of the ds_mutex that it locked previously. This causes safe_mutex to assert with the message: "Trying to unlock mutex LOCK_wait_commit that wasn't locked". The fix is to ensure that DEBUG_SYNC also will restore mysys_var->current_mutex in the case where the original value was NULL.	11 years ago
Kristian Nielsen	e79b7ca966	MDEV-7179: rpl.rpl_gtid_crash failed in buildbot with Warning: database page corruption or a failed I saw two test failures in rpl.rpl_gtid_crash where we get this in the error log: 141123 12:47:54 [Note] InnoDB: Restoring possible half-written data pages 141123 12:47:54 [Note] InnoDB: from the doublewrite buffer... InnoDB: Warning: database page corruption or a failed InnoDB: file read of space 6 page 3. InnoDB: Trying to recover it from the doublewrite buffer. 141123 12:47:54 [Note] InnoDB: Recovered the page from the doublewrite buffer. This test case deliberately crashes the server, and if this crash happens right in the middle of writing a buffer pool page to disk, it is not unexpected that we can get a half-written page. The page is recovered correctly from the doublewrite buffer. So this patch adds a suppression for this warning in the error log for this test case.	11 years ago
Kristian Nielsen	b79685902d	MDEV-6903: gtid_slave_pos is incorrect after master crash When a master slave restarts, it logs a special restart format description event in its binlog. When the slave sees this event, it knows it needs to roll back any active partial transaction, in case the master crashed previously in the middle of writing such transaction to its binlog. However, there was a bug where this rollback did not reset rgi->pending_gtid. This caused the @@gtid_slave_pos to be updated incorrectly with the GTID of the partial transaction that was rolled back. Fix this by always clearing rgi->pending_gtid in cleanup_context(), hopefully preventing similar bugs from turning up in other special cases where a transaction is rolled back during replication. Thanks to Pavel Ivanov for tracking down the issue and providing a test case.	11 years ago
Jan Lindström	f3bdf9d741	MDEV-7046: MySQL#74480 - Failing assertion: os_file_status(newpath, &exists, &type) after Operating system error number 36 in a file operation. Analysis: os_file_get_status did not handle error ENAMETOOLONG correctly. Fix: Add correct handling for error ENAMETOOLONG. Note that on InnoDB case the error is not passed all the way up to server. That would be bigger rewamp.	11 years ago
Jan Lindström	b62c4c6586	Better comments and add a test case.	11 years ago
Jan Lindström	e5802c38f9	Better comments and add a test case.	11 years ago
Jan Lindström	77a6abf311	MDEV-7183: innodb-wl5522-debug-zip fails in buildbot on Windows Problem is different path separators. Fixed by replacing result.	11 years ago
Jan Lindström	876106804e	MDEV-7169: innodb.innodb_bug14147491 fails in buildbot on Windows Problem is that test could open Microsoft C++ Client Debugger windows with abort exceptin. Lets not try to test this on windows.	11 years ago
Jan Lindström	b7cee6251a	MDEV-7168: Tests innodb.innodb_stats_create_table innodb.innodb_stats_drop_locked fail and innodb.innodb_stats_fetch_nonexistent fails in buildbot on Windows Analysis: Problem is that innodb_stats_create_on_corrupted test renames mysql.innodb.index_stats and all the rest are dependend on this table. Fix: After rename back to original, restart mysqld to make sure that table is correct.	11 years ago
Jan Lindström	ef1ba3b1e6	MDEV-7164: innodb.innodb-alter-table-disk-full fails in buildbot on Windows Analysis: Test case uses Linux specific error codes. Fix: Can't run test case with Windows currently because requires to inject error to system.	11 years ago
Alexey Botchkov	a726dbd634	MDEV-7157 plugins.server_audit fails sporadically in buildbot. Records can get to the different place in the log when multiple thread are logged. So the delay added to let the record be saved on the same place.	11 years ago
Sergei Golubchik	ffc0ef6316	5.5 merge	11 years ago
Jan Lindström	8ff66501ca	Forgot to add test file.	11 years ago
Sergey Vojtovich	4472a0ef95	MDEV-7026 - Race in InnoDB/XtraDB mutex implementation can stall or hang the server This is an addition to original patch. Added full memory barrier to ensure proper StoreLoad order between waiters and lock_word on PPC64.	11 years ago
Jan Lindström	b0febdb66e	MDEV-7084: innodb index stats inadequate using constant innodb_stats_sample_pages Use traditional statistics estimation by default (innodb-stats-traditional=true). There could be performance regression for customers if there is a lot of open table operations.	11 years ago
Sergei Golubchik	67e2e14627	Merge	11 years ago
Sergei Golubchik	82f56328ea	after merge fixes: * adjust viossl.c to take account the new code (SSL_get_error is used now, cannot simply remap it) * remove unnecessary version check * update the test to 10.0	11 years ago

1 2 3 4 5 ...

89829 Commits (16fb2963ff497b7c0b6371a3bd3f0345dc625815) All Branches Search

89829 Commits (16fb2963ff497b7c0b6371a3bd3f0345dc625815)

All Branches