Hi Rafal,
Rafal Somla, 22.09.2009 12:22:
> Changed time format?
Possible, but improbable. I have approved the original patch, which
included the respective change already:
=== modified file 'mysql-test/suite/backup/r/backup_logs.result'
...
@@ -255,7 +255,7 @@ backup_state complete
operation backup
error_num 0
num_objects 11
-total_bytes 4216
+total_bytes 4222
This added 6 bytes to the image size, which looks reasonable. The
current problem is a single added byte. I don't see a way, how this
could come from the new time format. Especially as the image contains
multiple fixed time fields.
>
> Ingo Strüwing wrote:
>> Hi Chuck, team,
>>
>> 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
>
--
Ingo Strüwing, Database Group
Sun Microsystems GmbH, Sonnenallee 1, D-85551 Kirchheim-Heimstetten
Geschäftsführer: Thomas Schröder, Wolfgang Engels, Wolf Frenkel
Vorsitzender des Aufsichtsrates: Martin Häring HRB München 161028
