Description:
On one platform, and by random it seems (I did rerun the test case),
the output seems to be in a different order than expected by the
"*.result" file. Question is, is this behavior expected?
If it is expected for the engine used, maybe a SORT BY or something
would make the test return the same result each time?
Diff included below. As I said, I can't reproduce it with the
same install as in the failure, so this is likely "random".
*** r/show_check.result Sat Oct 15 06:05:46 2005
--- r/show_check.reject Sat Oct 15 16:06:23 2005
***************
*** 520,539 ****
1
SHOW OPEN TABLES;
Database Table In_use Name_locked
! mysql db 0 0
test urkunde 0 0
mysql time_zone 0 0
mysql user 0 0
test txt1 0 0
! mysql proc 0 0
test tyt2 0 0
mysql time_zone_name 0 0
SHOW OPEN TABLES FROM mysql;
Database Table In_use Name_locked
! mysql db 0 0
mysql time_zone 0 0
mysql user 0 0
! mysql proc 0 0
mysql time_zone_name 0 0
SHOW OPEN TABLES FROM mysql LIKE 'u%';
Database Table In_use Name_locked
--- 520,539 ----
1
SHOW OPEN TABLES;
Database Table In_use Name_locked
! mysql proc 0 0
test urkunde 0 0
mysql time_zone 0 0
mysql user 0 0
test txt1 0 0
! mysql db 0 0
test tyt2 0 0
mysql time_zone_name 0 0
SHOW OPEN TABLES FROM mysql;
Database Table In_use Name_locked
! mysql proc 0 0
mysql time_zone 0 0
mysql user 0 0
! mysql db 0 0
mysql time_zone_name 0 0
SHOW OPEN TABLES FROM mysql LIKE 'u%';
Database Table In_use Name_locked
***************
*** 546,553 ****
mysql time_zone_name 0 0
SHOW OPEN TABLES LIKE '%o%';
Database Table In_use Name_locked
- mysql time_zone 0 0
mysql proc 0 0
mysql time_zone_name 0 0
FLUSH TABLES;
SHOW OPEN TABLES;
--- 546,553 ----
mysql time_zone_name 0 0
SHOW OPEN TABLES LIKE '%o%';
Database Table In_use Name_locked
mysql proc 0 0
+ mysql time_zone 0 0
mysql time_zone_name 0 0
FLUSH TABLES;
SHOW OPEN TABLES;
How to repeat:
Run the test suite lots of times :-)