summaryrefslogtreecommitdiff
path: root/mysql-test/suite
Commit message (Collapse)AuthorAgeFilesLines
* Adding multi_range_read support to partitionsMonty2017-09-091-2/+2
| | | | | | | | | | | | | | | Other things: - Cleanup of allocated bitmaps done in open(), which simplifies init_partition_bitmaps() - Add needed defines in ha_spider.cc to enable new spider code - Fixed some DBUG_PRINT() to be consistent with normal code - Removed end space - The changes in test cases partition_innodb, partition_range, partition_pruning etc are becasue partitions can now more exactly calculate the number of rows in a range. Contains spider patches: 014,015,023,033,035,037,040,042,044,045,049,050,051,053,059
* MDEV-7700 Spiral patch 002_mariadb-10.0.15.spider.diff, part 2Monty2017-09-092-2/+4
| | | | | | Allow partition engines to access table->s->connect_string for engines that uses HTON_CAN_READ_CONNECT_STRING_IN_PARTITION Don't reset table->s->connect_string in ha_partition::open
* Adjust the imported innodb.alter_crash test for MariaDBMarko Mäkelä2017-09-083-25/+27
| | | | trx_undo_assign_undo(): Restore the fault injection.
* MDEV-13626 Merge InnoDB test cases from MySQL 5.7 (part 1)Marko Mäkelä2017-09-082-0/+376
| | | | Import the test innodb.alter_crash
* Make a test more robustMarko Mäkelä2017-09-082-2/+2
| | | | | | The redo log is divided into 512-byte blocks. Sometimes, some of the strings end up at a block boundary and will not be found. Look for only one match.
* MDEV-13466 Implement --export option for MariaDB BackupVladislav Vaintroub2017-09-074-5/+24
| | | | | | | full server recovery is performed . We start "mysqld" with --bootstrap and pass bootstrap script consisting of several FLUSH TABLES FOR export/ UNLOCK TABLES
* Merge 10.1 into 10.2Marko Mäkelä2017-09-063-55/+13
|\
| * Follow-up to MDEV-13227: Shorten the testMarko Mäkelä2017-09-062-52/+12
| | | | | | | | | | | | | | The bug only affects ROW_FORMAT=DYNAMIC tables. It is reproducible already with 2 records in the table. Keep testing with ROW_FORMAT=REDUNDANT just in case.
| * Follow-up to MDEV-13227: Do not run unnecessary test combinationsMarko Mäkelä2017-09-062-3/+1
| | | | | | | | | | The bug only affected innodb_page_size=64k. There is no point running the test with smaller page sizes.
* | Fix nondeterministic failure of innodb.table_flagsMarko Mäkelä2017-09-062-1/+5
| | | | | | | | | | The files ibtmp1 and ib_buffer_pool are sometimes created, sometimes not. Remove them if they exist.
* | After-merge fix for a Galera test resultMarko Mäkelä2017-09-011-0/+2
| |
* | Fix test for MDEV-13674: Deprecate innodb_use_mtflush and innodb_mtflush_threadsMarko Mäkelä2017-09-011-1/+1
| |
* | Disable a badly written, randomly failing Galera testMarko Mäkelä2017-08-311-0/+1
| | | | | | | | | | | | | | | | CURRENT_TEST: galera.galera_kill_applier mysqltest: At line 14: query 'KILL $applier_thread' failed with wrong errno 1064: 'You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '' at line 1', instead of 1095...
* | MDEV-13674: Deprecate innodb_use_mtflush and innodb_mtflush_threadsbb-10.2-MDEV-13674Jan Lindström2017-08-311-2/+2
| | | | | | | | | | These parameters and associated code is to be removed in 10.3. Users can use innodb-page-cleaners > 1 instead.
* | Merge 10.1 into 10.2Marko Mäkelä2017-08-313-8/+13
|\ \ | |/
| * Fixed test failure on innodb_encryptionJan Lindström2017-08-313-8/+13
| | | | | | | | | | | | | | | | | | | | After MDEV-13583: Improvements for MTR rebootstrap introduced in MDEV-12042 bootsrap correctly creates mysql/innodb_table_stats and mysql/innodb_index_stats InnoDB tables before innodb_encryption test starts. These tables are also encrypted or decrypted, thus we need to wait also these tables (if not we could randomly get different results as system tablespace and these tables are encrypted or decrypted in parallel).
* | Fix some badly written Galera testsMarko Mäkelä2017-08-313-10/+72
| | | | | | | | | | | | | | | | | | | | | | | | galera.galera_kill_applier: Make the test less likely to fail by adding sleep time. galera.query_cache: Remove data truncation. Part of the test file looks like it has been misinterpreted as latin1 and wrongly converted to UTF-8 encoding. In MariaDB 10.1, the server would only warn about data truncation and not issue an error. 10.2 is stricter. (The test should be carefully reviewed if it really makes sense.)
* | Merge 10.1 into 10.2Marko Mäkelä2017-08-31149-309/+8665
|\ \ | |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | For running the Galera tests, the variable my_disable_leak_check was set to true in order to avoid assertions due to memory leaks at shutdown. Some adjustments due to MDEV-13625 (merge InnoDB tests from MySQL 5.6) were performed. The most notable behaviour changes from 10.0 and 10.1 are the following: * innodb.innodb-table-online: adjustments for the DROP COLUMN behaviour change (MDEV-11114, MDEV-13613) * innodb.innodb-index-online-fk: the removal of a (1,NULL) record from the result; originally removed in MySQL 5.7 in the Oracle Bug #16244691 fix https://github.com/mysql/mysql-server/commit/377774689bf6a16af74182753fe950d514c2c6dd * innodb.create-index-debug: disabled due to MDEV-13680 (the MySQL Bug #77497 fix was not merged from 5.6 to 5.7.10) * innodb.innodb-alter-autoinc: MariaDB 10.2 behaves like MySQL 5.6/5.7, while MariaDB 10.0 and 10.1 assign different values when auto_increment_increment or auto_increment_offset are used. Also MySQL 5.6/5.7 exhibit different behaviour between LGORITHM=INPLACE and ALGORITHM=COPY, so something needs to be tested and fixed in both MariaDB 10.0 and 10.2. * innodb.innodb-wl5980-alter: disabled because it would trigger an InnoDB assertion failure (MDEV-13668 may need additional effort in 10.2)
| * Temporarily disable encryption.innodb_encryption after the mergeMarko Mäkelä2017-08-301-0/+1
| |
| * Merge branch '10.0' into 10.1Marko Mäkelä2017-08-3033-0/+7023
| |\
| | * Merge innodb.create-index test changes from MySQL 5.6 to MariaDBMarko Mäkelä2017-08-292-0/+60
| | | | | | | | | | | | | | | | | | Import the MySQL 5.6 addition from innodb.create-index to a new debug-only test, innodb.create-index-debug. The existing test innodb.create-index also runs on a debug server.
| | * Adjust the imported MySQL 5.6 tests for MariaDBMarko Mäkelä2017-08-2921-123/+182
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | FIXME: MDEV-13668 InnoDB unnecessarily rebuilds table FIXME: MDEV-13671 InnoDB should use case-insensitive column name comparisons like the rest of the server FIXME: MDEV-13640 / Properly fix MDEV-9469 'Incorrect key file' on ALTER TABLE FIXME: investigate result difference in innodb.innodb-alter-autoinc and ensure that MariaDB does the right thing with auto_increment_increment and auto_increment_offset, for both ALGORITHM=INPLACE and ALGORITHM=COPY (Oracle MySQL behaviour differs between those two).
| | * MDEV-13625 Merge InnoDB test cases from MySQL 5.6 (part 1)Marko Mäkelä2017-08-2927-0/+6904
| | | | | | | | | | | | | | | Import some ALTER TABLE test cases from MySQL 5.6 without modification. The adjustments will be in a separate commit.
| * | Merge remote-tracking branch 'origin/bb-10.1-jplindst' into 10.1Jan Lindström2017-08-29104-307/+1447
| |\ \
| | * | Add galera suite to default suites and disable failing testbb-10.1-jplindstJan Lindström2017-08-283-2/+8
| | | | | | | | | | | | | | | | cases.
| | * | Merge remote-tracking branch 'origin/bb-10.1-galera' into 10.1Jan Lindström2017-08-24104-306/+1440
| | |\ \
| | | * | Fix Merge ErrorSachin Setiya2017-08-233-3/+3
| | | | |
| | | * | Merge remote-tracking branch 'origin/10.0-galera' into 10.1Jan Lindström2017-08-21101-303/+1437
| | | |\ \
| | | | * | Add galera_admin to disabled.Jan Lindström2017-08-211-0/+1
| | | | | |
| | | | * | Add more disabled test.Jan Lindström2017-08-202-2/+4
| | | | | |
| | | | * | Add more disabled tests and one ignored warning.Jan Lindström2017-08-192-1/+5
| | | | | |
| | | | * | Galera test fixes and add remaining test failures as disabled.Jan Lindström2017-08-1817-54/+93
| | | | | |
| | | | * | More test failure fixes.mariadb-galera-10.0.32Jan Lindström2017-08-165-0/+12
| | | | | |
| | | | * | Move galera_ist_progress and galera_ist_restart_joiner tests under big_test.Jan Lindström2017-08-162-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | This is because they could cause out of storage if run on /dev/shm.
| | | | * | Fix test failures.Jan Lindström2017-08-167-133/+37
| | | | | |
| | | | * | Fix test failure on test MW-86 and remove MW-360 test.Jan Lindström2017-08-1510-423/+238
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Merged from mysql-wsrep-bugs following: GCF-1058 MTR test galera.MW-86 fails on repeated runs Wait for the sync point sync.wsrep_apply_cb to be reached before executing the test and clearing the debug flag sync.wsrep_apply_cb. The race scenario: Intended behavior: node2: set sync.wsrep_apply_cb in order to start waiting in the background INSERT node1: INSERT start node2 (background): INSERT start node1: INSERT end node2: send signal to background INSERT: "stop waiting and continue executing" node2: clear sync.wsrep_apply_cb as no longer needed node2 (background): consume the signal node2 (background): INSERT end node2: DROP TABLE node2: check no pending signals are left - ok What happens occasionally (unexpected): node2: set sync.wsrep_apply_cb in order to start waiting in the background INSERT node1: INSERT start node2 (background): INSERT start node1: INSERT end // The background INSERT still has _not_ reached the place where it starts // waiting for the signal: // DBUG_EXECUTE_IF("sync.wsrep_apply_cb", "now wait_for..."); node2: send signal to background INSERT: "stop waiting and continue executing" node2: clear sync.wsrep_apply_cb as no longer needed // The background INSERT reaches DBUG_EXECUTE_IF("sync.wsrep_apply_cb", ...) // but sync.wsrep_apply_cb has already been cleared and the "wait" code is not // executed. The signal remains unconsumed. node2 (background): INSERT end node2: DROP TABLE node2: check no pending signals are left - failure, signal.wsrep_apply_cb is pending (not consumed) Remove MW-360 test case as it is not intended for MariaDB (uses MySQL GTID).
| | | | * | MW-369 Removing obsoleted testsTeemu Ollakka2017-08-148-323/+0
| | | | | |
| | | | * | Refs: MW-369 * fixed sync point usage in MW-369.inc, which made it ↵sjaakola2017-08-143-44/+370
| | | | | | | | | | | | | | | | | | | | | | | | impossible to run this test with --repeat option * moved all MW-369*.test tests into MW-369.test file, each as one separate test phase * added two more test phases, in MW-369.test file * tests MW-369A, MW-369B and MW-369C are obsolete after this commit
| | | | * | MW-369 Fixed test MW-369D, recorded MW-369C, MW-369DTeemu Ollakka2017-08-147-3/+71
| | | | | |
| | | | * | MW-369 MTR tests for foreign key conflictsTeemu Ollakka2017-08-147-0/+323
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Tests MW-369C, MW-369D haven't been recorded yet since the outcome from the tests is not what is desired.
| | | | * | Refs: MW-369 * added MTR test, which causes a crash in slave applying, due ↵sjaakola2017-08-141-0/+82
| | | | | | | | | | | | | | | | | | | | | | | | to FK constraint violation * mtr test is not deterministic, but can surface the crash, at least in my laptop
| | | | * | Galera MTR Tests: Fortify galera_ist_restart_joiner.test - remove DDLs, fix ↵Philip Stoev2017-08-142-27/+8
| | | | | | | | | | | | | | | | | | | | | | | | sync point handling
| | | | * | Galera MTR Tests: Stability fixesPhilip Stoev2017-08-1410-19/+23
| | | | | |
| | | | * | Galera MTR Tests: Test case for GAL-501 Improved URI parsing for IPv6 addressesPhilip Stoev2017-08-143-0/+78
| | | | | |
| | | | * | Galera MTR Tests: Extend test for MW-86 with additional SHOW commands (part #2)Philip Stoev2017-08-142-8/+196
| | | | | |
| | | | * | Galera MTR Tests: Extend test for MW-86 with additional SHOW commandsPhilip Stoev2017-08-141-0/+1
| | | | | |
| | | | * | Galera MTR Tests: Tests for MW-360 DROP TABLE containing temporary tables ↵Philip Stoev2017-08-145-0/+400
| | | | | | | | | | | | | | | | | | | | | | | | results in binlog divergence
| | | | * | MW-86 MTR test: check that SHOW commands no longer obey wsrep_sync_wait = 1Daniele Sciascia2017-08-142-0/+64
| | | | | |
| | | | * | MW-86 Adjust MTR tests for changes to wsrep_sync_waitDaniele Sciascia2017-08-1437-56/+205
| | | | | |
| | | | * | Galera MTR Tests: Tests for MW-366 - improved support for IPv6Philip Stoev2017-08-149-0/+278
| | | | | |
View Lorry Controller Status