Bug #37801 main.delay_key_write_func fails randomly on windows

• Submitted: 2 Jul 2008 10:56
• Modified: 9 Feb 2009 11:21
• Reporter: Alexander Nozdrin
• Status: Can't repeat
• Category: MySQL Server: Tests
• Severity: S3 (Non-critical)
• Version: 6.0-BK
• OS: Windows
• Assigned to: Horst Hunger
• CPU Architecture: Any
• Tags: pushbuild, sporadic, test failure

[2 Jul 2008 10:56] Alexander Nozdrin

Description:
--- C:/cygwin/home/pushbuild/pb1/pb/bzr_mysql-6.0-falcon/34/mysql-6.0.6-alpha-pb34/mysql-test/r/delay_key_write_func.result	2008-07-01 19:20:50.000000000 +0300
+++ C:\cygwin\home\pushbuild\pb1\pb\bzr_mysql-6.0-falcon\34\mysql-6.0.6-alpha-pb34\mysql-test\r\delay_key_write_func.reject	2008-07-01 21:52:14.859375000 +0300
@@ -15,6 +15,10 @@
 res_is_ALL
 ALL
 '#--------------------FN_DYNVARS_023_02-------------------------#'
+Warnings:
+Error	145	Table '.\mysql\proc' is marked as crashed and should be repaired
+Error	1194	Table 'proc' is marked as crashed and should be repaired
+Error	1034	1 client is using or hasn't closed the table properly
 '---check when delay_key_write is OFF---'
 SET @@global.delay_key_write = OFF;
 FLUSH STATUS;

How to repeat:
https://intranet.mysql.com/secure/pushbuild/xref.pl?startdate=&enddate=&dir=&plat=&testtyp...

[9 Feb 2009 11:21] Horst Hunger

The last failure occurred at Nov. 11th, 2008. Since that time the test run successfully on Windows systems. I also couldn't reproduce the failure.
Another point is the failure itself, that seems to be more dependent on the test environment and not on the test program or the server.