5.6 --repeat=2 test failures

Bug #1664473 reported by Laurynas Biveinis
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Status tracked in 5.7
5.5
Invalid
Undecided
Unassigned
5.6
Fix Released
Low
Laurynas Biveinis
5.7
Fix Released
Low
Laurynas Biveinis

Bug Description

On 5.6 trunk with --repeat=2, non-upstream testcases:

query_response_time.basic w3 [ fail ]
        Test ended at 2017-02-11 12:52:17

CURRENT_TEST: query_response_time.basic
--- /mnt/workspace/percona-server-5.6-repeat/BUILD_TYPE/debug/Host/amd64/MTR_REPEAT/2/plugin/query_response_time/tests/mtr/basic.result 2017-02-03 15:30:26.782453038 +0300
+++ /mnt/workspace/percona-server-5.6-repeat/BUILD_TYPE/debug/Host/amd64/MTR_REPEAT/2/build/mysql-test/var/3/log/basic.reject 2017-02-11 20:52:17.561762046 +0300
@@ -47,4 +47,4 @@
 SET GLOBAL QUERY_RESPONSE_TIME_STATS=default;
 SELECT SUM(COUNT) FROM INFORMATION_SCHEMA.QUERY_RESPONSE_TIME;
 SUM(COUNT)
-3
+6

mysqltest: Result content mismatch

tags: added: ci query-response-time
Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote :

innodb.xtradb_rseg_bug_1260259 w2 [ fail ]
        Test ended at 2017-02-11 13:07:33

CURRENT_TEST: innodb.xtradb_rseg_bug_1260259
mysqltest: At line 19: command "remove_file" failed with error 1. my_errno=2

tags: added: xtradb
Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote :

main.bug1432494 w1 [ pass ] 6
main.bug1432494 w1 [ fail ]
        Test ended at 2017-02-11 13:19:01

CURRENT_TEST: main.bug1432494
mysqltest: At line 12: query 'SET @@GLOBAL.master_info_repository="TABLE"' failed: 1750: Failure while changing the type of replication repository: Multiple replication metadata repository instances found with data in them. Unable to decide which is the correct one to choose.

The result from queries just before the failure was:
SET SESSION AUTOCOMMIT=0;
SET @old_master_info_repository=@@GLOBAL.master_info_repository;
safe_process[7442]: Child process: 7443, exit: 1

Server [mysqld.1 - pid: 7375, winpid: 7375] log:
Server log from this test:
----------SERVER LOG START-----------
2017-02-11 21:19:01 7376 [ERROR] Error changing the type of master info's repository: Multiple replication metadata repository instances found with data in them. Unable to decide which is the correct one to choose.
----------SERVER LOG END-------------

Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote :
Download full text (10.9 KiB)

innodb.percona_changed_page_bmp w1 [ fail ] Found warnings/errors in server log file!
        Test ended at 2017-02-11 13:57:46
line
2017-02-11 21:55:58 7f17fc4ee940 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
.... repeated 1 times: f17fc4ee940 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2017-02-11 21:55:58 7f17fc4ee940 InnoDB: Error: Fetch of persistent statistics requested for table "test"."t1" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2017-02-11 21:56:02 7fea27187940 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2017-02-11 21:56:02 7fea27187940 InnoDB: Error: Fetch of persistent statistics requested for table "test"."t1" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2017-02-11 21:56:07 7f9ee3358940 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2017-02-11 21:56:07 7f9ee3358940 InnoDB: Error: Fetch of persistent statistics requested for table "test"."t1" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2017-02-11 21:56:12 7fae247a3940 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2017-02-11 21:56:12 7fae247a3940 InnoDB: Error: Fetch of persistent statistics requested for table "test"."t1" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2017-02-11 21:56:22 7fae06f1d940 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
.... repeated 3 times: fae06f1d940 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2017-02-11 21:57:02 7fae247a3940 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
.... repeated 1 times: fae247a3940 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2017-02-11 21:57:02 7fae247a3940 InnoDB: Error: Fetch of persistent statistics requested for table "test"."t2" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2017-02-11 21:57:06 7f24722f6940 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2017-02-11 21:57:06 7f24722f6940 InnoDB: Error: Fetch of persistent statistics requested for table "test"."t1" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2017-02-11 21:57:11 7f7b1ccc7940 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2017-02-11 21:57:11 7f7b1ccc7940 InnoDB: Error: Fetch of persistent statistics requested for table "test"."t1" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2017-02-11 21:57:20 7f283bea1940 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
.... repeate...

tags: added: bitmap
Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote :

innodb.percona_changed_page_bmp_log_block_size w4 [ fail ] Found warnings/errors in server log file!
        Test ended at 2017-02-11 14:15:12
line
2017-02-11 22:15:05 15297 [Warning] InnoDB: last tracked LSN in './ib_modified_log_2_2038923.xdb' is 2038923, but the last checkpoint LSN is 2039820. This might be due to a server crash or a very fast shutdown.
^ Found warnings in /mnt/workspace/percona-server-5.6-repeat/BUILD_TYPE/debug/Host/amd64/MTR_REPEAT/2/build/mysql-test/var/4/log/mysqld.1.err
ok

Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote :

innodb.percona_innodb_deadlock_count w4 [ pass ] 29
innodb.percona_innodb_deadlock_count w4 [ fail ]
        Test ended at 2017-02-11 14:16:46

CURRENT_TEST: innodb.percona_innodb_deadlock_count
mysqltest: In included file "./include/assert.inc":
included from ./include/assert.inc at line 75:
At line 74: Test assertion failed in assert.inc

The result from queries just before the failure was:
# Establish connection con1 (user=root)
# Establish connection con2 (user=root)
# Create test table
create table t(a INT PRIMARY KEY, b INT) engine=InnoDB;
# Insert two rows to test table
insert into t values(2,1);
insert into t values(1,2);
SET GLOBAL innodb_monitor_reset = lock_deadlocks;
# Switch to connection con1
BEGIN;
SELECT b FROM t WHERE a=1 FOR UPDATE;
# Switch to connection con2
BEGIN;
SELECT b FROM t WHERE a=2 FOR UPDATE;
# Switch to connection con1
SELECT b FROM t WHERE a=2 FOR UPDATE;
# Switch to connection con2
SELECT b FROM t WHERE a=1 FOR UPDATE;
# Switch to connection con1
ROLLBACK;
# Switch to connection con2
ROLLBACK;
# Switch to connection default
SELECT COUNT INTO @lock_deadlocks_var FROM INFORMATION_SCHEMA.INNODB_METRICS WHERE NAME='lock_deadlocks';
include/assert.inc [Exactly one deadlock should have been found]
######## Test assertion failed: Exactly one deadlock should have been found ########
Dumping debug info:
Assertion text: 'Exactly one deadlock should have been found'
Assertion condition: '@lock_deadlocks_var = 1'
Assertion condition, interpolated: '@lock_deadlocks_var = 1'
Assertion result: '0'
safe_process[16242]: Child process: 16243, exit: 1

Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote :

tokudb.bugs.leak172 w3 [ pass ] 20105
tokudb.bugs.leak172 w3 [ fail ]
        Test ended at 2017-02-11 16:08:05

CURRENT_TEST: tokudb.bugs.leak172
mysqltest: At line 13: command "copy_file" failed with error 1. my_errno=17

The result from queries just before the failure was:
set default_storage_engine=tokudb;
drop table if exists t1,t2;

Warnings from just before the error:
Note 1051 Unknown table 'test.t1'
safe_process[926]: Child process: 927, exit: 1

Server [mysqld.1 - pid: 31946, winpid: 31946] log:
Server log from this test:
----------SERVER LOG START-----------

tags: added: tokudb
Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote :
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-2238

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.