Bug #47725 NDB: Sporadically, MTR reports that tests have not cleaned up properly!

• Submitted: 29 Sep 2009 18:38
• Reporter: Luis Soares
• Status: Verified
• Category: Tests: Cluster
• Severity: S3 (Non-critical)
• Version: 5.1
• OS: Any
• CPU Architecture: Any

[29 Sep 2009 18:38] Luis Soares

Description:
I had observed the following in my local environment:

rpl_ndb.rpl_ndb_commit_afterflush        [ pass ]  48170

MTR's internal check of the test case 'rpl_ndb.rpl_ndb_commit_afterflush' 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
'/home/lsoares/Workspace/mysql-server/bugfix/b34582/mysql-5.1-bugteam/mysql-test/var/tmp/c
heck-mysqld_2_1.log'.
mysqltest: Results saved in
'/home/lsoares/Workspace/mysql-server/bugfix/b34582/mysql-5.1-bugteam/mysql-test/var/tmp/c
heck-mysqld_2_1.result'.
mysqltest: Connecting to server localhost:13004 (socket /tmp/FqkE2bx91h/mysqld.2.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.
---
/home/lsoares/Workspace/mysql-server/bugfix/b34582/mysql-5.1-bugteam/mysql-test/var/tmp/ch
eck-mysqld_2_1.result     2009-07-21 20:46:34.000000000 +0300
+++
/home/lsoares/Workspace/mysql-server/bugfix/b34582/mysql-5.1-bugteam/mysql-test/var/tmp/ch
eck-mysqld_2_1.reject     2009-07-21 20:47:23.000000000 +0300
@@ -509,7 +509,3 @@
 mysql.time_zone_transition     3895294076
 mysql.time_zone_transition_type        168184411
 mysql.user     680030170
-Warnings:
-Error  1296    Got error 4009 'Cluster Failure' from NDB 
-Error  1296    Got error 4009 'Cluster Failure' from NDB 
-Error  1296    Got error 4009 'Cluster Failure' from NDB 

mysqltest: Result length mismatch

not ok

However, after verifying some logs in PB, I have realized that this is not exclusive to my local env. It repeats in PB runs. Check the how to repeat section for details.

How to repeat:
Check PB2 logs for tree mysql-5.1-rep+2:

Push: http://pb2.norway.sun.com/web.py?template=push_details&push=548747
Logs: http://pb2.norway.sun.com/web.py?action=archive_download&archive_id=777292&pretty=please

You will find the warning repeating itself on several ndb test cases.

Suggested fix:
n/a