MySQL Bugs: #42515: MTR2: spurious state check failures

Bug #42515	MTR2: spurious state check failures
Submitted:	1 Feb 2009 13:36	Modified:	10 Feb 2011 14:50
Reporter:	Sergey Petrunya	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Tools: MTR / mysql-test-run	Severity:	S3 (Non-critical)
Version:		OS:	Any
Assigned to:	Bjørn Munch	CPU Architecture:	Any

Description:
I am seeing test check failures like this:

https://intranet.mysql.com/secure/pushbuild/getlog.pl?dir=bzr_mysql-6.0-opt&entry=Sergey_P...

main.fulltext_plugin                     [ pass ]     18

MTR's internal check of the test case 'main.fulltext_plugin' 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:
--- /dev/shm/var-n_mix-110/tmp/check-mysqld_1.result	2009-01-30 23:00:19.094319250 +0300
+++ /dev/shm/var-n_mix-110/tmp/check-mysqld_1.reject	2009-01-30 23:00:20.902432250 +0300
@@ -53,9 +53,9 @@
 DEADLOCK_TIMEOUT_SHORT	10000
 GROUP_CONCAT_MAX_LEN	1024
 CONCURRENT_INSERT	1
-LOG_BACKUP_OUTPUT	TABLE
+RANGE_ALLOC_BLOCK_SIZE	4096
 COLLATION_DATABASE	latin1_swedish_ci
-OPTIMIZER_PRUNE_LEVEL	1
+LOG_BACKUP_OUTPUT	TABLE
 FT_MIN_WORD_LEN	4
 LOG_SLOW_QUERIES	ON
 INIT_SLAVE	
@@ -134,7 +134,7 @@
 FALCON_GOPHER_THREADS	5
 QUERY_PREALLOC_SIZE	8192
 RAND_SEED1	
-RANGE_ALLOC_BLOCK_SIZE	4096
+OPTIMIZER_PRUNE_LEVEL	1
 NET_READ_TIMEOUT	30
 MAX_SEEKS_FOR_KEY	18446744073709551615
 QUERY_CACHE_LIMIT	1048576

mysqltest: Result content mismatch

not ok

main.udf                                 [ pass ]    196

Apparently the variables have all the same values, they are just listed in a different order.  I have no idea why variables might be listed in different order but I don't consider that a state change that's worth reporting.

How to repeat:
see above

Suggested fix:
Fix MTR2 to ignore such differences?

Duplicate of Bug#42508?

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

No feedback