Hi Ingo,
I am checking this now. I have an Ubuntu 8.04 64-bit machine.
There are several ideas that come to mind as to the cause. The first and
foremost is that something may have changed in the way the metadata
CREATE statements are built. To test this, I would take a backup of a
database on a pre-merged tree then again on the merged tree and do a
compare (diff) on the two backup image files. I suspect you will see
something very minor in the metadata.
Of course, if it isn't that then I am not certain where to look. But
then again, a diff of the two image files might give us a clue. ;)
Chuck
> after a merge of mysql-6.0-backup and mysql-6.0-codebase, I get the
> following failure on my local Linux x86_64 machine:
>
> backup.backup_logs w4 [ fail ]
> Test ended at 2009-09-21 20:08:29
>
> CURRENT_TEST: backup.backup_logs
> ---
>
> /home2/mydev/bzrtest/testdir-6.0-backup-merge-1/mysql-test/suite/backup/r/backup_logs.result
> 2009-09-21 20:23:44.000000000 +0300
> +++
>
> /home2/mydev/bzrtest/testdir-6.0-backup-merge-1/mysql-test/suite/backup/r/backup_logs.reject
> 2009-09-21 21:08:29.000000000 +0300
> @@ -255,7 +255,7 @@
> operation backup
> error_num 0
> num_objects 11
> -total_bytes 4222
> +total_bytes 4223
> validity_point_time #
> start_time #
> stop_time #
> @@ -324,7 +324,7 @@
> operation restore
> error_num 0
> num_objects 11
> -total_bytes 4222
> +total_bytes 4223
> validity_point_time #
> start_time #
> stop_time #
>
> Do you know what could be the reason?
>
> Regards
> Ingo
