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: Patch pending 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

[19 Jul 2013 23:28] Davi Arnaut
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.
[20 Jul 2013 8:07] MySQL Verification Team
Hello Davi,

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

Thanks,
Umesh
[28 May 1:12] MySQL Admin
Posted by developer: Bug status updated to 'Patch pending'

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.052 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.