| Bug #41359 | backup.backup_errors fails after merge of main and backup trees | ||
|---|---|---|---|
| Submitted: | 10 Dec 2008 15:36 | Modified: | 11 Feb 2009 3:16 |
| Reporter: | Ingo Strüwing | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Backup | Severity: | S3 (Non-critical) |
| Version: | 6.0.9 | OS: | Linux |
| Assigned to: | Jørgen Løland | CPU Architecture: | Any |
[10 Dec 2008 16:14]
Ingo Strüwing
The merge has revision-id: ingo.struewing@sun.com-20081210155306-n9f5l3nmea1obn39 Suggested triage values: Defect class minor. Wrong warnings. Workaround acceptable. Ignore the warnings. Impact minimal. This is not in the main trees yet.
[15 Dec 2008 12:18]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/61663 2738 Jorgen Loland 2008-12-15 Bug#41359 - backup.backup_errors fails after merge of main and backup trees Test backup_errors failed because SHOW WARNINGS after a successful backup statement may return warnings from previous statements. This is a temporary fix to quickly reenable the test. A proper fix will be submitted in bug 41468
[15 Dec 2008 15:48]
Rafal Somla
OK to push.
[15 Dec 2008 16:07]
Øystein Grøvlen
Patch approved.
[17 Dec 2008 9:00]
Jørgen Løland
Pushed to team tree Dec 16
[2 Feb 2009 16:06]
Bugs System
Pushed into 6.0.10-alpha (revid:sergefp@mysql.com-20090202090240-dlkxhmc1asrar5rl) (version source revid:sergefp@mysql.com-20090129100938-qvke7a9krg24l8pl) (merge vers: 6.0.10-alpha) (pib:6)
[11 Feb 2009 3:16]
Paul DuBois
Noted in 6.0.10 changelog. BACKUP DATABASE and RESTORE did not reset the message list displayed by SHOW WARNINGS.
Description: After merge of mysql-6.0 and mysql-6.0-backup, I get: backup.backup_errors [ fail ] --- /home2/mydev/bzrtest/testdir-6.0-backup-merge-1/mysql-test/suite/backup/r/backup_errors.result 2008-12-09 12:40:29.000000000 +0300 +++ /home2/mydev/bzrtest/testdir-6.0-backup-merge-1/mysql-test/suite/backup/r/backup_errors.reject 2008-12-10 13:43:25.000000000 +0300 @@ -21,6 +21,8 @@ # SHOW WARNINGS; Level Code Message +Error # Can't create/write to file '/home2/mydev/bzrtest/testdir-6.0-backup-merge-1/mysql-test/var/master-data/bdb/t1.frm' (Errcode: 17) +Error # Can't write to backup location 'bdb/t1.frm' BACKUP DATABASE adb TO "test.bak"; ERROR HY000: Can't create/write to file 'MYSQLTEST_VARDIR/master-data/test.bak' (Errcode: #) SHOW WARNINGS; mysqltest: Result content mismatch This is a repitition of the warnings from the former statement, though the current statement uses test.bak instead of bdb/t1.frm. I guess, the warnings have not be cleared between the statements. Top revision from mysql-6.0: 2773 Alexander Nozdrin 2008-12-08 [merge] revision-id:alik@sun.com-20081208112915-alxg2mejaq7i1dhx Merge from 6.0 Top revision from mysql-6.0-backup: 2732 oystein.grovlen@sun.com 2008-12-08 revision-id:oystein.grovlen@sun.com-20081208103021-ljm9pabojqf9k3jf Bug#40741 backup.backup test fails if blackhole engine is not available - Make sure test backup.backup only runs if blackhole engine is available. - Fixed have_blackhole.inc to give an informative message when a test is skipped because the blackhole engine is missing - Some clean-up to backup.backup result file to cater for changes that has happened while it was disabled. I will disable the test case. Please re-enable after fix. How to repeat: Branch the merged revision from mysql-6.0-backup-merge. I will push it there after creating the bug report.