Test innodb.monitor is unstable

Bug #1684264 reported by Laurynas Biveinis on 2017-04-19
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

innodb.monitor w3 [ fail ]
        Test ended at 2017-04-08 20:22:43

CURRENT_TEST: innodb.monitor
--- /mnt/workspace/percona-server-5.6-trunk/BUILD_TYPE/release/Host/ubuntu-precise-32bit/mysql-test/suite/innodb/r/monitor.result 2017-04-01 15:06:32.309929915 +0300
+++ /mnt/workspace/percona-server-5.6-trunk/BUILD_TYPE/release/Host/ubuntu-precise-32bit/build/mysql-test/var/3/log/monitor.reject 2017-04-08 16:22:41.261401919 +0300
@@ -563,7 +563,7 @@
 SELECT NAME, COUNT FROM INFORMATION_SCHEMA.INNODB_METRICS WHERE NAME
 LIKE 'buffer_page_written_index_leaf';
 NAME COUNT
-buffer_page_written_index_leaf NNNN
+buffer_page_written_index_leaf NNNN0
 SET GLOBAL innodb_monitor_disable='module_buffer_page';
 SET GLOBAL innodb_monitor_reset_all='module_buffer_page';
 SELECT NAME, COUNT FROM INFORMATION_SCHEMA.INNODB_METRICS WHERE NAME

mysqltest: Result content mismatch

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

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

Other bug subscribers