He Zhenxing wrote:
> Hi Alfranio,
>
> I'd suggest to avoid the copy_file problem by rewriting that part of the
> test like this, copy the file to slave as a new relay log, and use
> CHANGE MASTER to change the SQL threads' relay log file and position
> accordingly, and then start slave sql thread to replay the statements.
> By this way, the test can avoid replacing an existing binary log file.
>
> You can look into binlog_auto_increment_bug33029.test for an example.
>
Thanks for the advice.
I will do it
Cheers.
> Alfranio Correia wrote:
>
>> #At
> file:///home/acorreia/workspace.sun/repository.mysql/bzrwork/bug-43264/mysql-5.0-bugteam/
> based on revid:davi.arnaut@stripped
>>
>> 2770 Alfranio Correia 2009-06-12
>> BUG#43264 Test rpl_trigger is failing randomly w/ use of copy_file in 5.0
>>
>> Disabled the rpl_trigger on Windows due to the lack of mysqltest/mtr's
>> facilities to make it run properly.
>>
>> The test case fails sporadically on Windows while trying to overwrite an
> unused
>> binary log. The problem stems from the fact that MySQL on Windows does not
>> immediately unlock/release a file while the process that opened and closed
> it is
>> still running. In BUG#38603, this issue was circumvented by stopping the
> MySQL
>> process, copying the file and then restarting the MySQL process.
> Unfortunately,
>> such facilities are not available in the 5.0.
>>
>> modified:
>> mysql-test/t/rpl_trigger.test
>> === modified file 'mysql-test/t/rpl_trigger.test'
>> --- a/mysql-test/t/rpl_trigger.test 2009-02-19 20:37:40 +0000
>> +++ b/mysql-test/t/rpl_trigger.test 2009-06-12 03:36:40 +0000
>> @@ -3,6 +3,7 @@
>> #
>>
>> source include/master-slave.inc;
>> +source include/not_windows.inc;
>>
>> #
>> # #12482: Triggers has side effects with auto_increment values
>>
>>
>
>
