MySQL Bugs: #56695: MEB tests find mysql-stderr and mysql-stdout

Bug #56695	MEB tests find mysql-stderr and mysql-stdout
Submitted:	9 Sep 2010 16:27	Modified:	1 Dec 2010 23:35
Reporter:	Ingo Strüwing	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Enterprise Backup	Severity:	S2 (Serious)
Version:	3.5.next	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
When some tests are run together, the following happens:

...
 ibdata2
 mtr
 mysql
+mysql-stderr
+mysql-stdout
 test
...

mysqltest: Result content mismatch

Recent changes in MEB abandoned from the use of mysql-stderr and mysql-stdout.
But backup images in mysql-test/suite/meb/std_data still contain these files.
Some compatibility tests restore them in datadir.
Even if innobackup/mysqlbackup --copy_back is used, it would not filter out these files as they are no longer used in the current version.

How to repeat:
Run --suite=meb with a current meb.

Suggested fix:
IMHO, the best fix would be to re-package the zip files without mysql-stderr and mysql-stdout. I don't see any need for these files.

An alternative could be to remove the files in the test cases after unpackaging the zip files.

A former version of the product made the equivalent of:

  mysql ... > backup-dir/mysql-stdout 2> backup-dir/mysql-stderr

These files have been zipped into an std_data file with the whole backup_dir.

During restore, after unzipping the file, the former version did not restore these files in datadir. Since the current version does not create these files itself, it does not suppress their restore either.

The latest checkin into into mysql-5.1-meb for WL#5513 by Ritheesh on 2010-09-29 seems to have fixed this issue. Ritheesh, can you confirm ?

After WL5513 push, this is not an issue anymore. Setting the bug to "Documenting"