| Bug #11905 | Missing drop of tables used in rpl_deadlock causes subsequent test to fail | ||
|---|---|---|---|
| Submitted: | 13 Jul 2005 9:33 | Modified: | 17 Aug 2005 18:01 |
| Reporter: | Mats Kindahl | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server | Severity: | S3 (Non-critical) |
| Version: | 4.1 and up | OS: | Any (all) |
| Assigned to: | Elliot Murphy | CPU Architecture: | Any |
[27 Jul 2005 22:34]
Mike Hillyer
There is not enough information to document this. What version was this added to?
[28 Jul 2005 6:04]
Mats Kindahl
The fix has been added 4.1 and up, i.e., to 4.1, 5.0, and 5.1.
[6 Aug 2005 22:35]
Mike Hillyer
Changelog entries can only be made for three-part version numbers. Reverted to patch approved.
[17 Aug 2005 4:08]
Elliot Murphy
Looking at the source tarballs from the web download, this fix made it into 4.1.13a and 5.0.11. Thanks!
[17 Aug 2005 18:01]
Paul DuBois
Actually, I think no changelog entries are necessary. This is simply a fix to an erroneous test case script. Setting to Closed.
Description: In the rpl_deadlock suite, the two tables t3 and t4 are created of InnoDB type. The tables are not subsequently dropped at the end of the test, which causes subsequent tests that create any of those tables of InnoDB type to fail. How to repeat: The following ./mysql-test-run --start-from=rpl_deadlock --skip-ndb --mysqld=--binlog-format=row will cause the rpl_row_basic_3innodb (only in unreleased version) test to fail.