| Bug #47513 | Test main.merge_recover fails | ||
|---|---|---|---|
| Submitted: | 22 Sep 2009 10:16 | Modified: | 22 Sep 2009 10:20 |
| Reporter: | Ingo Strüwing | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Server: Options | Severity: | S3 (Non-critical) |
| Version: | 6.0.14 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | pbfail | ||
[22 Sep 2009 10:20]
Ingo Strüwing
Minor defect, it's just an additional warning. No workaround know with respect to the failing test case. Widespread impact, it makes all test runs fail.
Description: main.merge_recover w3 [ fail ] Test ended at 2009-09-21 20:09:00 CURRENT_TEST: main.merge_recover --- /home2/mydev/bzrtest/testdir-6.0-backup-merge-1/mysql-test/r/merge_recover.result 2009-09-02 12:57:58.000000000 +0300 +++ /home2/mydev/bzrtest/testdir-6.0-backup-merge-1/mysql-test/r/merge_recover.reject 2009-09-21 21:09:00.000000000 +0300 @@ -15,6 +15,8 @@ # set global table_open_cache=256; set global table_definition_cache=256; +Warnings: +Warning 1292 Truncated incorrect table_definition_cache value: '256' drop procedure if exists p_create; create procedure p_create() begin mysqltest: Result content mismatch How to repeat: See also Xref http://pb2.norway.sun.com/web.py?template=mysql_show_test_failure&test_failure_id=&test_ou...