summaryrefslogtreecommitdiff
path: root/mysql-test
Commit message (Collapse)AuthorAgeFilesLines
* MDEV-11097 - Update the list of unstable testsElena Stepanova2016-10-231-53/+36
|
* Upstream MIPS test fixes from Debian Bug 838557.Kristian Nielsen2016-10-212-3/+3
| | | | | | https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838557 MIPS has a different errno for "directory not empty".
* MDEV-11061 Valgrind builder produces endless warningsElena Stepanova2016-10-161-10/+107
| | | | OpenSSL problems, part II
* More unstable testsElena Stepanova2016-10-141-0/+3
|
* MDEV-11061 Valgrind builder produces endless warnings after switching to OpenSSElena Stepanova2016-10-141-0/+22
|
* Merge branch '5.5' into 10.0Sergei Golubchik2016-09-292-5/+53
|\
| * MDEV-10907 MTR and server writes can interleave in the error logVladislav Vaintroub2016-09-272-5/+53
| | | | | | | | | | Ensure atomic appends to the error log by using CreateFile with FILE_APPEND_DATA flag to open error log file (both MTR and server)
* | Merge branch '5.5' into 10.0Sergei Golubchik2016-09-2717-334/+160
|\ \ | |/
| * MDEV-10441 Document the server_audit_loc_info variableSergei Golubchik2016-09-262-6/+0
| | | | | | | | | | fix PLUGIN_VAR_NOSYSVAR | PLUGIN_VAR_NOCMDOPT plugin thdvars to work. use that for server_audit_loc_info
| * Windows , mtr : allow cdb to print core dumps also if --parallel > 1Vladislav Vaintroub2016-09-261-5/+1
| |
| * fix BIGINT+MEDIUMINT type aggregationmariadb-5.5.52Sergei Golubchik2016-09-122-0/+27
| |
| * potential signedness issueSergei Golubchik2016-09-122-0/+8
| | | | | | | | | | | | different fix for 07a33cdcef: Bug #23296299 : HANDLE_FATAL_SIGNAL (SIG=11) IN MY_TOSORT_UTF32
| * Merge branch 'mysql/5.5' into 5.5Sergei Golubchik2016-09-114-280/+19
| |\ | | | | | | | | | 80% reverted
| | * Bug #23280699: MYSQLD GOT SIGNAL 11 IN IS_NULL ON SELECTSreeharsha Ramanavarapu2016-07-222-10/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | FROM I_S Issue: ------ There is a difference in the field type created when the following DDLs are used: 1) CREATE TABLE t0 AS SELECT NULL; 2) CREATE TABLE t0 AS SELECT GREATEST(NULL,NULL); The first statement creates field of type Field_string and the second one creates a field of type Field_null. This creates a problem when the query mentioned in this bug is used. Since the null_ptr is calculated differently for Field_null. Solution: --------- When there is a function returning null in the select list as mentioned above, the field should be of type Field_string. This was fixed in 5.6+ as part of Bug#14021323. This is a backport to mysql-5.5. An incorrect comment in innodb_bug54044.test has been corrected in all versions.
| | * Bug#14111584 PB2: PERFSCHEMA.AGGREGATE FAILS ON PB2 SPORADICALLYChristopher Powers2016-06-302-276/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Permanently removed test case perfschema.aggregate. The Performance Schema is generally lock-free, allowing for race conditions that might arise from multi-threaded operation which occasionally results in temporary and/or minor variances when aggregating statistics. This test needs to be redesigned to accommodate such variances.
| * | MDEV-8833 Crash of server on prepared statement with conversion to semi-joinOleksandr Byelkin2016-09-022-2/+60
| | | | | | | | | | | | Correct context chain made to allow outer fields pullout.
| * | DEV-10595 MariaDB daemon leaks memory with specific queryMonty2016-08-252-0/+29
| | | | | | | | | | | | | | | The issue was that in some extreme cases when doing GROUP BY, buffers for temporary blobs where not properly cleared.
| * | MDEV-10424 - Assertion `ticket == __null' failed in MDL_request::set_typeSergey Vojtovich2016-08-172-0/+30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Reexecution of prepared "ANALYZE TABLE merge_table, table" may miss to reinitialize "table" for subsequent execution and trigger assertion failure. This happens because MERGE engine may adjust table->next_global chain, which gets cleared by close_thread_tables()/ha_myisammrg::detach_children() later. Since reinitilization iterates next_global chain, it won't see tables following merge table. Fixed by appending saved next_global chain after merge children.
* | | MDEV-10775 System table in InnoDB format allowed in MariaDB could lead to crashSergei Golubchik2016-09-232-0/+20
| | | | | | | | | | | | | | | when opening a system table for a SELECT-like read, pretend (for the sake of engines) it's SQLCOM_SELECT
* | | Update contributorsiangilfillan2016-09-191-0/+1
| | |
* | | Debian bug#837369 - test failures on hppaKristian Nielsen2016-09-112-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ENOTEMPTY is 247 on hppa, not 39 like on Linux, according to this report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837369 So add another replacement for this to rpl.rpl_drop_db and binlog.binlog_databasae tests (there were already a couple similar replacements for other platforms). Signed-off-by: Kristian Nielsen <knielsen@knielsen-hq.org>
* | | Fix use of `require` in mysql-test-run.Kristian Nielsen2016-09-103-10/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The motivation for this is that Perl is moving towards not having current directory ./ in @INC by default. This is causing mysql-test-run.pl to fail in latest Debian Unstable: https://lists.debian.org/debian-devel-announce/2016/08/msg00013.html However, we have `use "lib"`, there is no need for current directory in @INC, except for a gross hack. In mtr_cases.pm, there is a `require "mtr_misc.pl"`, which hides mtr_misc.pl away in mtr_cases namespace. And things only work because mysql-test-run.pl loads it with a different name, `require "lib/mtr_misc.pl"`! (Perl will `require` only once for each unique filename). Fix this by only using `require` in main program, and referencing functions with :: scope from other namespaces. For multi-use in different namespaces, proper `use` modules should be used. Signed-off-by: Kristian Nielsen <knielsen@knielsen-hq.org>
* | | MDEV-7142: main.index_merge_innodb fails sporadically in buildbotSergei Petrunia2016-09-053-0/+7
| | | | | | | | | | | | Attempt to stabilize the testcase.
* | | MDEV-10604 Create a list of unstable MTR tests to be disabled in ↵mariadb-10.0.27Elena Stepanova2016-08-242-3/+274
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | distribution builds - mysql-test/unstable-tests list is created, it includes = tests identified as unstable by Debian; = tests which failed in buildbot on 10.0 over the last ~6 months and were not fixed; = tests which have been recently modified or newly added - '*' wildcard is now supported in skip lists
* | | MDEV-10630 rpl.rpl_mdev6020 fails in buildbot with timeoutMonty2016-08-222-2/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The issue was that when running with valgrind the wait for master_pos_Wait() was not long enough. This patch also fixes two other failures that could affect rpl_mdev6020: - check_if_conflicting_replication_locks() didn't properly check domains - 'did_mark_start_commit' was after signals to other threads was sent which could get the variable read too early.
* | | Fixed "Packets out of order" warning message on stdout in clients,Monty2016-08-212-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | compiled for debugging, when the server goes down This happens in the following scenario: - Server gets a shutdown message - Servers sends error ER_CONNECTION_KILLED to the clients connection - The client sends a query to the server, before the server has time to close the connection to the client - Client reads the ER_CONNECTION_KILLED error message In the above case, the packet number for the reply is one less than what the client expected and the client prints "Packets out of order". Fixed the following way: - The client accepts now error packages with a packet number one less than expected. - To ensure that this issue can be detected early in my_real_read(), error messages sent to the client are not compressed, even when compressed protocol is used.
* | | Added new status variables to make it easier to debug certain problems:Monty2016-08-2137-96/+286
| | | | | | | | | | | | | | | | | | - Handler_read_retry - Update_scan - Delete_scan
* | | Cleanups and minor fixesMonty2016-08-212-3/+15
| | | | | | | | | | | | | | | | | | | | | | | | - Fixed typos - Added --core-on-failure to mysql-test-run - More DBUG_PRINT in viosocket.c - Don't forget CLIENT_REMEMBER_OPTIONS for compressed slave protocol - Removed not used stage variables
* | | Merge branch 'bb-10.0-serg' into 10.0Sergei Golubchik2016-08-1437-61/+964
|\ \ \
| * | | after merge fixesSergei Golubchik2016-08-101-0/+56
| | | |
| * | | Merge branch '5.5' into 10.0Sergei Golubchik2016-08-1036-61/+908
| |\ \ \ | | |/ /
| | * | MDEV-10465 general_log_file can be abusedSergei Golubchik2016-08-094-0/+8
| | | | | | | | | | | | | | | | Windows!
| | * | MDEV-6128:[PATCH] mysqlcheck wrongly escapes '.' in table namesSergei Golubchik2016-08-082-4/+119
| | | | | | | | | | | | | | | | | | | | | | | | | | | | a correct fix: * store properly quoted table names in tables4repair/etc lists * tell handle_request_for_tables whether the name is aalready properly quoted * test cases for all uses of fix_table_name()
| | * | MDEV-10465 general_log_file can be abusedSergei Golubchik2016-08-084-0/+8
| | | | | | | | | | | | | | | | followup
| | * | MDEV-10468 Assertion `nr >= 0.0' failed in Item_sum_std::val_real()Alexander Barkov2016-08-082-0/+18
| | | |
| | * | MDEV-10500 CASE/IF Statement returns multiple values and shifts further ↵Alexander Barkov2016-08-082-0/+52
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | result values to the next column We assume all around the code that null_value==true is in sync with NULL value returned by val_str()/val_decimal(). Item_sum_sum::val_decimal() erroneously returned a non-NULL value together with null_value set to true. Fixing to return NULL instead.
| | * | MDEV-10506 Protocol::end_statement(): Assertion `0' failed upon ALTER TABLESergei Golubchik2016-08-072-0/+231
| | | | | | | | | | | | | | | | thd->clear_error() destroyed already existing error status
| | * | MDEV-9946: main.xtradb_mrr fails sporadicallySergei Petrunia2016-08-042-4/+4
| | | | | | | | | | | | | | | | Make the testcase stable by adding FORCE INDEX
| | * | MDEV-10465 general_log_file can be abusedSergei Golubchik2016-08-034-0/+32
| | | | | | | | | | | | | | | | | | | | This issue was discovered by Dawid Golunski (http://legalhackers.com)
| | * | MDEV-10350 "./mtr --report-features" doesn't workSergei Golubchik2016-08-032-30/+0
| | | | | | | | | | | | | | | | removed
| | * | MDEV-7329 plugins.pam_cleartext fails sporadically in buildbotSergei Golubchik2016-08-032-1/+4
| | | | | | | | | | | | | | | | | | | | wait until the failed connection thread completely dies before uninstalling pam plugin
| | * | improve pam_cleartext.test a bitSergei Golubchik2016-08-032-2/+15
| | | |
| | * | Merge branch 'mysql/5.5' into 5.5Sergei Golubchik2016-08-039-2/+262
| | |\ \ | | | |/ | | | | | | | | without a fix for Bug#12818255 (MDEV-6581)
| | | * BUG#23080148 - BACKPORT BUG 14653594 AND BUG 20683959 TOThayumanavar S2016-06-203-2/+50
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | MYSQL-5.5 The bug asks for a backport of bug#1463594 and bug#20682959. This is required because of the fact that if replication is enabled, master transaction can commit whereas slave can't commit due to not exact 'enviroment'. This manifestation is seen in bug#22024200.
| | | * Bug #23279858: MYSQLD GOT SIGNAL 11 ON SIMPLE SELECTSreeharsha Ramanavarapu2016-05-242-0/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | NAME_CONST QUERY ISSUE: ------ Using NAME_CONST with a non-constant negated expression as value can result in incorrect behavior. SOLUTION: --------- The problem can be avoided by checking whether the argument is a constant value. The fix is a backport of Bug#12735545.
| | | * BUG#21142859: FUNCTION UPDATING A VIEW FAILS TO FIND TABLEKarthik Kamath2016-05-182-0/+46
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | THAT ACTUALLY EXISTS ANALYSIS: ========= Stored functions updating a view where the view table has a trigger defined that updates another table, fails reporting an error that the table doesn't exist. If there is a trigger defined on a table, a variable 'trg_event_map' will be set to a non-zero value after the parsed tree creation. This indicates what triggers we need to pre-load for the TABLE_LIST when opening an associated table. During the prelocking phase, the variable 'trg_event_map' will not be set for the view table. This value will be set after the processing of triggers defined on the table. During the processing of sub-statements, 'locked_tables_mode' will be set to 'LTM_PRELOCKED' which denotes that further locking of tables/functions cannot be done. This results in the other table not being locked and thus further processing results in an error getting reported. FIX: ==== During the prelocking of view, the value of 'trg_event_map' of the view is copied to 'trg_event_map' of the next table in the TABLE_LIST. This results in the locking of tables associated with the trigger as well.
| | | * Bug#23251517: SEMISYNC REPLICATION HANGINGSujatha Sivakumar2016-05-136-329/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Revert following bug fix: Bug#20685029: SLAVE IO THREAD SHOULD STOP WHEN DISK IS FULL Bug#21753696: MAKE SHOW SLAVE STATUS NON BLOCKING IF IO THREAD WAITS FOR DISK SPACE This fix results in a deadlock between slave IO thread and SQL thread.
| | | * Bug#12818255: READ-ONLY OPTION DOES NOT ALLOWSujatha Sivakumar2016-05-042-0/+148
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | INSERTS/UPDATES ON TEMPORARY TABLES Bug#14294223: CHANGES NOT ALLOWED TO TEMPORARY TABLES ON READ-ONLY SERVERS Problem: ======== Running 5.5.14 in read only we can create temporary tables but can not insert or update records in the table. When we try we get Error 1290 : The MySQL server is running with the --read-only option so it cannot execute this statement. Analysis: ========= This bug is very specific to binlog being enabled and binlog-format being stmt/mixed. Standalone server without binlog enabled or with row based binlog-mode works fine. How standalone server and row based replication work: ===================================================== Standalone server and row based replication mark the transactions as read_write only when they are modifying non temporary tables as part of their current transaction. Because of this when code enters commit phase it checks if a transaction is read_write or not. If the transaction is read_write and global read only mode is enabled those transaction will fail with 'server is read only mode' error. In the case of statement based mode at the time of writing to binary log a binlog handler is created and it is always marked as read_write. In case of temporary tables even though the engine did not mark the transaction as read_write but the new transaction that is started by binlog handler is considered as read_write. Hence in this case when code enters commit phase it finds one handler which has a read_write transaction even when we are modifying temporary table. This causes the server to throw an error when global read-only mode is enabled. Fix: ==== At the time of commit in "ha_commit_trans" if a read_write transaction is found, we should check if this transaction is coming from a handler other than binlog_handler. This will ensure that there is a genuine read_write transaction being sent by the engine apart from binlog_handler and only then it should be blocked.
| | * | MDEV-10467 Assertion `nr >= 0.0' failed in Item_sum_std::val_real()Alexander Barkov2016-08-032-0/+24
| | | | | | | | | | | | | | | | Backporting MDEV-5781 from 10.0.
| | * | MDEV-10383 Named pipes : multiple servers can listen on the same pipenameVladislav Vaintroub2016-08-021-0/+9
| | | | | | | | | | | | | | | | | | | | Use FILE_FLAG_FIRST_PIPE_INSTANCE with the first CreateNamedPipe() call to make sure the pipe does not already exist.
View Lorry Controller Status