mtr internal check of INNODB_FILE_FORMAT_CHECK fails in debug builds
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS |
Fix Released
|
Undecided
|
Unassigned | ||
5.1 |
Fix Released
|
Critical
|
Alexey Kopytov |
Bug Description
http://
(all debug builds)
First occurs:
rpl.rpl_
MTR's internal check of the test case 'rpl.rpl_
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. It could also be caused by the previous test run
by this thread, if the server wasn't restarted.
This is the diff of the states of the servers before and after the
test case was executed:
mysqltest: Logging to '/jenkins/
mysqltest: Results saved in '/jenkins/
mysqltest: Connecting to server localhost:13000 (socket /tmp/WCjGnx4Rbk
mysqltest: ... Connected.
mysqltest: Start processing test commands from './include/
mysqltest: ... Done processing test commands.
--- /jenkins/
+++ /jenkins/
@@ -101,7 +101,7 @@
INNODB_
INNODB_
INNODB_FILE_FORMAT Antelope
-INNODB_
+INNODB_
INNODB_
INNODB_
INNODB_
mysqltest: Result content mismatch
Related branches
- Stewart Smith: Pending requested
-
Diff: 579 lines (+124/-207)1 file modifiedmysql-test.diff (+124/-207)
- Stewart Smith (community): Approve
-
Diff: 19 lines (+3/-2)1 file modifiedpatches/mysql-test.diff (+3/-2)
Changed in percona-server: | |
status: | New → Fix Released |
Also observed for a valgrind build: jenkins. percona. com/job/ percona- server- 5.1-valgrind/ BUILD_TYPE= valgrind, Host=ubuntu- natty-64bit/ 1/console
http://
innodb_ plugin. innodb_ bug60049 w4 [ pass ] 2471
MTR's internal check of the test case 'innodb_ plugin. innodb_ bug60049' failed. workspace/ percona- server- 5.1-valgrind/ BUILD_TYPE/ valgrind/ Host/ubuntu- natty-64bit/ Percona- Server- 5.1.57/ mysql-test/ var/4/tmp/ check-mysqld_ 1.log'. workspace/ percona- server- 5.1-valgrind/ BUILD_TYPE/ valgrind/ Host/ubuntu- natty-64bit/ Percona- Server- 5.1.57/ mysql-test/ var/4/tmp/ check-mysqld_ 1.result' . /4/mysqld. 1.sock) as 'root', connection 'default', attempt 0 ... check-testcase. test' ... workspace/ percona- server- 5.1-valgrind/ BUILD_TYPE/ valgrind/ Host/ubuntu- natty-64bit/ Percona- Server- 5.1.57/ mysql-test/ var/4/tmp/ check-mysqld_ 1.result 2011-06-09 04:07:14.846099000 +0300 workspace/ percona- server- 5.1-valgrind/ BUILD_TYPE/ valgrind/ Host/ubuntu- natty-64bit/ Percona- Server- 5.1.57/ mysql-test/ var/4/tmp/ check-mysqld_ 1.reject 2011-06-09 04:07:17.556099003 +0300 FAST_RECOVERY OFF FAST_SHUTDOWN 0 FILE_FORMAT_ CHECK Antelope FILE_FORMAT_ CHECK Barracuda FILE_PER_ TABLE OFF FLUSH_LOG_ AT_TRX_ COMMIT 1 FLUSH_LOG_ AT_TRX_ COMMIT_ SESSION 3
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. It could also be caused by the previous test run
by this thread, if the server wasn't restarted.
This is the diff of the states of the servers before and after the
test case was executed:
mysqltest: Logging to '/jenkins/
mysqltest: Results saved in '/jenkins/
mysqltest: Connecting to server localhost:13030 (socket /tmp/gSnVireLp6
mysqltest: ... Connected.
mysqltest: Start processing test commands from './include/
mysqltest: ... Done processing test commands.
--- /jenkins/
+++ /jenkins/
@@ -99,7 +99,7 @@
INNODB_
INNODB_
INNODB_FILE_FORMAT Antelope
-INNODB_
+INNODB_
INNODB_
INNODB_
INNODB_
mysqltest: Result content mismatch
not ok