Bug #53663 Test "binlog_delete_and_flush_index" fails on Windows: wrong path name reporting
Submitted: 14 May 2010 21:43
Reporter: Joerg Bruehe Email Updates:
Status: Verified Impact on me:
None 
Category:Tests: Server Severity:S3 (Non-critical)
Version:5.0.91 OS:Microsoft Windows
Assigned to: CPU Architecture:Any
Triage: Triaged: D3 (Medium)

[14 May 2010 21:43] Joerg Bruehe
Description:
This failure report is from the build of 5.0.91, but the same failure already happened in 5.0.90. As that was the version in which the test was introduced, it never succeeded on Windows.

The output:
=====
binlog_delete_and_flush_index  [ fail ]

mysqltest: In included file "./include/show_binlog_events.inc": At line 10: query 'show binlog events from $binlog_start' failed: 29: File '/cygdrive/d/mysql-5.0.91-winbuild/mysql-5.0.91-winx64/mysql-test' not found (Errcode: 2)

The result from queries just before the failure was:
< snip >

### assertion: show original binlogs
show binary logs;
Log_name        File_size
master-bin.000001       #
### assertion: binlog contents from regular entries
show binlog events from <binlog_start>;
Log_name        Pos     Event_type      Server_id       End_log_pos     Info
master-bin.000001       #       Query   #       #       use `test`; CREATE TABLE t1 (a int)
FLUSH LOGS;
### assertion: index file contains renamed binlog and the new one
SET @index=LOAD_FILE('MYSQLD_DATADIR/master-bin.index');
SELECT @index;
@index
/cygdrive/d/mysql-5.0.91-winbuild/mysql-5.0.91-winx64/mysql-test
MYSQLD_DATADIR/master-bin.000002

### assertion: original binlog content still exists, despite we
###            renamed and changed the index file
show binlog events from <binlog_start>;

More results from queries before failure can be found in /PATH/mysql-test/var/log/binlog_delete_and_flush_index.log

Warnings from just before the error:
Error 29 File '/cygdrive/d/mysql-5.0.91-winbuild/mysql-5.0.91-winx64/mysql-test' not found (Errcode: 2)

Stopping All Servers
=====

The path names obviously vary by build host and configuration, but the problem happens on both 32 and 64 bit builds, in all configurations.

How to repeat:
Build and test.
[18 May 2010 10:06] Joerg Bruehe
This bug was seen in 5.0 only, neither in 5.1 nor 5.5 (until now).