| Bug #50191 | Result mismatch in backup_check_i_s due to differences in IS DB in 5.x and 6.0 | ||
|---|---|---|---|
| Submitted: | 8 Jan 2010 18:53 | Modified: | 8 Jan 2010 21:20 |
| Reporter: | Hema Sridharan | Email Updates: | |
| Status: | Patch queued | Impact on me: | |
| Category: | MySQL Server: Backup | Severity: | S3 (Non-critical) |
| Version: | OS: | Any | |
| Assigned to: | Assigned Account | CPU Architecture: | Any |
[8 Jan 2010 18:58]
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/96431 3045 Hema Sridharan 2010-01-08 BUG#50191 (Result mismatch in backup_check_i_s due to result differences in IS DB in 5.x and 6.0) This patch will overwrite the result file for backup_check_i_s.test modified: mysql-test/suite/backup/r/backup_check_i_s.result
[8 Jan 2010 19:12]
Hema Sridharan
Marking tick for Ingo as he approved in IRC
[8 Jan 2010 20:22]
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/96433 3047 Hema Sridharan 2010-01-08 BUG#50191(backup_check_i_s test fails due to differences in IS DB in 5.x and 6.0) This patch will overwrite the result file for this test. modified: mysql-test/suite/backup/r/backup_check_i_s.result
[8 Jan 2010 21:17]
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/96439 3047 Hema Sridharan 2010-01-08 BUG#50191(bakcup_check_i_s test fails due to differences in IS DB in 5.x and 6.0) This patch will overwrite the result file modified: mysql-test/suite/backup/r/backup_check_i_s.result
Description: The backup_check_i_s test fails in new backport tree(mysql-backup-backport) because of the differences in information schema database in 5.x and 6.0 How to repeat: ./mysql-test-run.pl --suite=backup backup_check_i_s.test ============================================================================== TEST RESULT TIME (ms) ------------------------------------------------------------ worker[1] Using MTR_BUILD_THREAD 300, with reserved ports 13000..13009 backup.backup_check_i_s [ fail ] Test ended at 2010-01-08 19:42:49 CURRENT_TEST: backup.backup_check_i_s --- @@ -35,8 +35,7 @@ TABLE_COLLATION varchar(32) YES NULL CHECKSUM bigint(21) unsigned YES NULL CREATE_OPTIONS varchar(255) YES NULL -TABLE_COMMENT varchar(2048) NO -TABLESPACE_NAME varchar(64) YES NULL +TABLE_COMMENT varchar(80) NO DESCRIBE columns; Field Type Null Key Default Extra TABLE_CATALOG varchar(512) NO @@ -57,9 +56,7 @@ COLUMN_KEY varchar(3) NO EXTRA varchar(27) NO PRIVILEGES varchar(80) NO -COLUMN_COMMENT varchar(1024) NO -STORAGE varchar(8) NO -FORMAT varchar(8) NO +COLUMN_COMMENT varchar(255) NO @@ -226,7 +216,6 @@ GLOBAL_STATUS GLOBAL_VARIABLES KEY_COLUMN_USAGE -PARAMETERS PARTITIONS PLUGINS PROCESSLIST @@ -245,3 +234,10 @@ TRIGGERS USER_PRIVILEGES VIEWS +INNODB_CMP_RESET +INNODB_TRX +INNODB_CMPMEM_RESET +INNODB_LOCK_WAITS +INNODB_CMPMEM +INNODB_CMP +INNODB_LOCKS The information_schema database has additional tables in 5.x INNODB_CMP_RESET | | INNODB_TRX | | INNODB_CMPMEM_RESET | | INNODB_LOCK_WAITS | | INNODB_CMPMEM | | INNODB_CMP | | INNODB_LOCKS Therefore, we just overwrite the result file for this test as there is no specific mismatch found due to MySQL backup.