Bug #21219 Test "mysqldump" needs to cleanup first

• Submitted: 21 Jul 2006 17:07
• Modified: 6 Nov 2006 14:50
• Reporter: Joerg Bruehe
• Status: Closed
• Category: MySQL Server: Tests
• Severity: S3 (Non-critical)
• Version: 4.1.21
• OS: Any (all)
• Assigned to: Magnus Blåudd
• CPU Architecture: Any

[21 Jul 2006 17:07] Joerg Bruehe

Description:
Detected during 4.1.21 release builds on Windows,
but it is a general problem affecting all versions and platforms:

Test "mysqldump" contains (when checking for bug#2592) this line:
   --exec $MYSQL_DUMP --compact test
(and later some variations of it).

When a previous test crashes, it may leave tables in database "test", which then get dumped and so change the "mysqldump" test output, causing this test to fail
(in my case: tables "t03" and "t04" from crashing "mysqlbinlog", bug#21218).

To protect against this, the test should ensure that database "test" is in a well-defined state when the test starts.

How to repeat:
Start the test "mysqldump" on a database which contains some un-expected table.

Suggested fix:
Either check for all tables in database "test" and drop them at test start,
or initialize the database before starting the test.

[21 Jul 2006 20:11] Magnus Blåudd

From 5.0 and up we are restoring a snapshot of a clean db up after a failed test case.

Will see what can be done about it in 4.1(Not much...)

[6 Nov 2006 14:50] Paul DuBois

Test suite change. No changelog entry needed.