Bug #64127 | MTR --warnings option misses some of InnoDB errors and warnings | ||
---|---|---|---|
Submitted: | 25 Jan 2012 9:29 | Modified: | 9 Jan 2015 10:18 |
Reporter: | Laurynas Biveinis (OCA) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Tools: MTR / mysql-test-run | Severity: | S3 (Non-critical) |
Version: | 5.1 bzr revno 3670, 5.5 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | Contribution |
[25 Jan 2012 9:29]
Laurynas Biveinis
[25 Jan 2012 10:07]
Valeriy Kravchuk
Thank you for the problem report and fix contributed. Verified just as described with current 5.1.62 from bzr (revno 3673) on 64-bit Linux FC14.
[27 Sep 2012 9:58]
Laurynas Biveinis
This bug has been fixed and may be closed. Thank you. In 5.1: revno: 3676 committer: sayantan.dutta@oracle.com branch nick: mysql-5.1 timestamp: Tue 2012-01-31 17:09:32 +0530 message: Bug #64127: MTR --warnings option misses some of InnoDB errors and warnings In 5.5: ------------------------------------------------------------ revno: 3654.1.5 [merge] committer: sayantan.dutta@oracle.com branch nick: mysql-5.5 timestamp: Tue 2012-01-31 17:20:56 +0530 message: merge #64127 5.1 => 5.5 ------------------------------------------------------------ revno: 2661.799.6 committer: sayantan.dutta@oracle.com branch nick: mysql-5.1 timestamp: Tue 2012-01-31 17:09:32 +0530 message: Bug #64127: MTR --warnings option misses some of InnoDB errors and warnings