percona_extended_innodb_status test is unstable

Bug #1607606 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
Fix Released
Low
Laurynas Biveinis
5.6
Fix Released
Low
Laurynas Biveinis
5.7
Fix Released
Low
Laurynas Biveinis

Bug Description

Test percona_extended_innodb_status sometimes fails with

innodb.percona_extended_innodb_status w4 [ fail ]
        Test ended at 2016-07-27 14:24:17

CURRENT_TEST: innodb.percona_extended_innodb_status
--- /mnt/workspace/percona-server-5.5-trunk/BUILD_TYPE/release/Host/centos5-32/mysql-test/suite/innodb/r/percona_extended_innodb_status.result 2016-06-30 21:03:06.743156797 +0300
+++ /mnt/workspace/percona-server-5.5-trunk/BUILD_TYPE/release/Host/centos5-32/mysql-test/suite/innodb/r/percona_extended_innodb_status.reject 2016-07-27 21:24:17.642521132 +0300
@@ -24,7 +24,7 @@
 UPDATE t SET value = 1 WHERE id = 3;
 connection default
 "Record lock" found
-n = 4
+n = 10
 ROLLBACK;
 connection con1
 ROLLBACK;
@@ -38,7 +38,7 @@
 UPDATE t SET value = 1 WHERE id = 3;
 connection default
 "Record lock" found
-n = 12
+n = 18
 ROLLBACK;
 connection con1
 ROLLBACK;
@@ -52,7 +52,7 @@
 UPDATE t SET value = 1 WHERE id = 3;
 connection default
 "Record lock" found
-n = 4
+n = 10
 too many locks printed
 ROLLBACK;
 connection con1
@@ -67,7 +67,7 @@
 UPDATE t SET value = 1 WHERE id = 3;
 connection default
 "Record lock" found
-n = 4
+n = 10
 ROLLBACK;
 connection con1
 ROLLBACK;

mysqltest: Result content mismatch

Tags: ci
tags: added: ci
Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote :
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-2162

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.