innodb.innodb fails on 11.0

[Aleksandr Kuzminsky]

innodb.innodb [ fail ]
        Test ended at 2010-06-01 01:43:49

CURRENT_TEST: innodb.innodb
--- /home/buildbot/slaves/percona-server-51-11/CentOS-5-x86-64/build/Percona-Server/mysql-test/suite/innodb/r/innodb.result 2010-06-01 08:29:49.000000000 +0300
+++ /home/buildbot/slaves/percona-server-51-11/CentOS-5-x86-64/build/Percona-Server/mysql-test/suite/innodb/r/innodb.reject 2010-06-01 08:44:50.000000000 +0300
@@ -1740,7 +1740,7 @@
 drop table t1;
 SELECT variable_value FROM information_schema.global_status WHERE LOWER(variable_name) = 'innodb_buffer_pool_pages_total';
 variable_value
-8192
+8191
 SELECT variable_value FROM information_schema.global_status WHERE LOWER(variable_name) = 'innodb_page_size';
 variable_value
 16384

mysqltest: Result content mismatch

[Yasufumi Kinoshita (yasufumi-kinoshita)]

It is not critical. mysql-5.5.4 's mysql test allows the value 8191 also. I will fix the script to allow the value also along with 5.5.4

[Shahriyar Rzayev (rzayev-sehriyar)]

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