MySQL Bugs: #69799: MTR does not check for warnings in the test log

Bug #69799	MTR does not check for warnings in the test log
Submitted:	19 Jul 2013 23:28	Modified:	20 Jul 2013 8:07
Reporter:	Davi Arnaut (OCA)	Email Updates:
Status:	Verified	Impact on me:	None
Category:	Tools: MTR / mysql-test-run	Severity:	S3 (Non-critical)
Version:	5.5,5.6	OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	mtr, valgrind, warnings

View
Add Comment
Files
Developer
Edit Submission
View Progress Log
Contributions

Description:
MTR currently does not check the mysqltest log for warnings. For example, although it is possible to run mysqltest under valgrind with --valgrind-mysqltest, any warnings printed are not going to be detected as MTR does not check the test log (that is, the "current_test" log file) for warnings.

How to repeat:
Run a test case that causes mysqltest to spew warnings:

foo.test:
--enable_ps_protocol
--enable_reconnect
select 1;

$ ./mtr --record test
$ ./mtr --ps-protocol --valgrind-mysqltest foo

Check var/log/mysqltest.log for warnings.

Hello Davi,

Thank you for the bug report and the test case. 
Verified as described.

Thanks,
Umesh