summaryrefslogtreecommitdiff
path: root/mysql-test/suite/innodb/t/innodb-mdev7046.test
Commit message (Collapse)AuthorAgeFilesLines
* Merge 10.4 into 10.5Marko Mäkelä2023-01-031-0/+2
|\
| * MDEV-30233 DROP DATABASE test fails: Directory not emptyMarko Mäkelä2022-12-151-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Some tests drop the default mtr database "test". This may fail due to the directory not being empty. InnoDB may not delete all tables immediately, due to the "background drop table queue" or its replacement in commit 1bd681c8b3c5213ce1f7976940a7dc38b48a0d39 (the purge of history would clean up after a DDL operation during which the server was killed). Let us try to avoid "drop database test" whenever it is easily possible. Where it is not, SET GLOBAL innodb_max_purge_lag_wait=0 will ensure that the replacement of the "background drop table queue" will have completed its job.
* | MDEV-18650: Options deprecated in previous versions - storage_engineVicențiu Ciorbaru2020-02-131-1/+1
|/ | | | | | | Remove usage of deprecated variable storage_engine. It was deprecated in 5.5 but it never issued a deprecation warning. Make it issue a warning in 10.5.1. Replaced with default_storage_engine.
* Updated mtr files to support different compiled in optionsMonty2019-09-011-5/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This allows one to run the test suite even if any of the following options are changed: - character-set-server - collation-server - join-cache-level - log-basename - max-allowed-packet - optimizer-switch - query-cache-size and query-cache-type - skip-name-resolve - table-definition-cache - table-open-cache - Some innodb options etc Changes: - Don't print out the value of system variables as one can't depend on them to being constants. - Don't set global variables to 'default' as the default may not be the same as the test was started with if there was an additional option file. Instead save original value and reset it at end of test. - Test that depends on the latin1 character set should include default_charset.inc or set the character set to latin1 - Test that depends on the original optimizer switch, should include default_optimizer_switch.inc - Test that depends on the value of a specific system variable should set it in the test (like optimizer_use_condition_selectivity) - Split subselect3.test into subselect3.test and subselect3.inc to make it easier to set and reset system variables. - Added .opt files for test that required specfic options that could be changed by external configuration files. - Fixed result files in rockdsb & tokudb that had not been updated for a while.
* MDEV-16456 InnoDB error "returned OS error 71" complains about wrong pathMarko Mäkelä2018-06-121-3/+3
| | | | | | | | | | | When attempting to rename a table to a non-existing database, InnoDB would misleadingly report "OS error 71" when in fact the error code is InnoDB's own (OS_FILE_NOT_FOUND), and not report both pathnames. Errors on rename could occur due to reasons connected to either pathname. os_file_handle_rename_error(): New function, to report errors in renaming files.
* Merge InnoDB 5.7 from mysql-5.7.9.Jan Lindström2016-09-021-0/+1
| | | | | | | | | | | | | | | | | | | | | | | Contains also MDEV-10547: Test multi_update_innodb fails with InnoDB 5.7 The failure happened because 5.7 has changed the signature of the bool handler::primary_key_is_clustered() const virtual function ("const" was added). InnoDB was using the old signature which caused the function not to be used. MDEV-10550: Parallel replication lock waits/deadlock handling does not work with InnoDB 5.7 Fixed mutexing problem on lock_trx_handle_wait. Note that rpl_parallel and rpl_optimistic_parallel tests still fail. MDEV-10156 : Group commit tests fail on 10.2 InnoDB (branch bb-10.2-jan) Reason: incorrect merge MDEV-10550: Parallel replication can't sync with master in InnoDB 5.7 (branch bb-10.2-jan) Reason: incorrect merge
* Fix test failure innodb-mdev7046 on Windows. Test causesJan Lindström2015-02-101-0/+2
| | | | | OS error printout from InnoDB.
* Fix try for Buildbot test failure for testsJan Lindström2015-01-161-0/+1
| | | | | | | innodb_bug12400341 innodb-mdev7046 innodb_stats_fetch_nonexistent
* MDEV-7262: innodb.innodb-mdev7046 fail on BuildBotJan Lindström2015-01-131-2/+3
| | | | | | | Test causes OS error printout and we need to supress this error message on tests. Additionally, test could cause different error codes on different OSs.
* Fix test case to allow success on create table (Windows).Jan Lindström2014-12-101-2/+2
|
* Add possibility to success on Windows.Jan Lindström2014-12-041-1/+2
|
* MDEV-7242: innodb.innodb-mdev7046 fails in various ways on buildbotJan Lindström2014-12-021-0/+11
| | | | | | | 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.
* add a proper cleanup to innodb.innodb-mdev7046 testSergei Golubchik2014-12-011-0/+3
|
* MDEV-7046: MySQL#74480 - Failing assertion: os_file_status(newpath, &exists, ↵Jan Lindström2014-11-251-0/+31
&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.
View Lorry Controller Status