Affects Version/s: None
Fix Version/s: None
**Reported in Launchpad by Alexey Kopytov last update 24-09-2013 14:51:51
After updating PS version used by the test suite from PS 5.6.10 to PS 5.6.11 (i.e. the one where page tracking is available), xb_incremental_bitmap_misc.sh fails in debug xtradb56 builds as follows:
incremental backup from 9000 is enabled.
xtrabackup: uses posix_fadvise().
xtrabackup: cd to /mnt/workspace/percona-xtrabackup-2.1-param/BUILD_TYPE/debug/Host/centos5-64/xtrabackuptarget/xtradb56/test/var/w1/var1/data
xtrabackup: using the following InnoDB configuration:
xtrabackup: innodb_data_home_dir = ./
xtrabackup: innodb_data_file_path = ibdata1:10M:autoextend
xtrabackup: innodb_log_group_home_dir = ./
xtrabackup: innodb_log_files_in_group = 2
xtrabackup: innodb_log_file_size = 50331648
>> log scanned up to (1634133)
InnoDB: Allocated tablespace 6, old maximum was 0
2013-07-22 12:10:05 2acfb2ea2580 InnoDB: Assertion failure in thread 47071548286336 in file changed_page_bitmap.cc line 404
InnoDB: Failing assertion: bitmap_files->files.start_lsn == first_file_start_lsn
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: about forcing recovery.
inc/common.sh: line 70: 6377 Aborted (core dumped) "$@"
2013-07-22 12:10:05: run.sh: ===> xtrabackup_56 failed with exit code 134