main.innodb-analyze internal check failed on 5.1.36

Bug #395778 reported by Aleksandr Kuzminsky
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona-XtraDB
Fix Released
Undecided
Aleksandr Kuzminsky

Bug Description

main.innodb-analyze [ pass ] 43

MTR's internal check of the test case 'main.innodb-analyze' failed.
This means that the test case does not preserve the state that existed
before the test case was executed. Most likely the test case did not
do a proper clean-up.
This is the diff of the states of the servers before and after the
test case was executed:
mysqltest: Logging to '/mnt/data1/home/buildbot/xtradb/Centos5_x86_64/mysql-5.1.36/mysql-test/var/tmp/check-mysqld_1.log'.
mysqltest: Results saved in '/mnt/data1/home/buildbot/xtradb/Centos5_x86_64/mysql-5.1.36/mysql-test/var/tmp/check-mysqld_1.result'.
mysqltest: Connecting to server localhost:13000 (socket /mnt/data1/home/buildbot/xtradb/Centos5_x86_64/mysql-5.1.36/mysql-test/var/tmp/mysqld.1.sock) as 'root', connection 'default', attempt 0 ...
mysqltest: ... Connected.
mysqltest: Start processing test commands from './include/check-testcase.test' ...
mysqltest: ... Done processing test commands.
--- /mnt/data1/home/buildbot/xtradb/Centos5_x86_64/mysql-5.1.36/mysql-test/var/tmp/check-mysqld_1.result 2009-07-05 16:59:13.000000000 +0300
+++ /mnt/data1/home/buildbot/xtradb/Centos5_x86_64/mysql-5.1.36/mysql-test/var/tmp/check-mysqld_1.reject 2009-07-05 16:59:14.000000000 +0300
@@ -118,7 +118,7 @@
 INNODB_STATS_AUTO_UPDATE 1
 INNODB_STATS_METHOD nulls_equal
 INNODB_STATS_ON_METADATA ON
-INNODB_STATS_SAMPLE_PAGES 8
+INNODB_STATS_SAMPLE_PAGES 16
 INNODB_STRICT_MODE OFF
 INNODB_SUPPORT_XA ON
 INNODB_SYNC_SPIN_LOOPS 20

mysqltest: Result content mismatch

Changed in percona-xtradb:
assignee: nobody → Aleksandr Kuzminsky (akuzminsky)
summary: - main.innodb-analyze internal check failed
+ main.innodb-analyze internal check failed on 5.1.36
Changed in percona-xtradb:
status: New → Fix Committed
Changed in percona-xtradb:
status: Fix Committed → Fix Released
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.