On Do, 2008-07-03 at 11:23 +0200, Vladislav Vaintroub wrote:
> I see, you still have not read the bug description.
> If you did, you would know ,the only possibility to fail randomly for this bug is a
> deadlock.
>
Vlad, please stop full quote and answer on top. It makes a thread less
readable.
1) What errors do you see when running falcon_bug_37080.test so that you
used --disable_abort_on_error?
2) I read the bug report otherwise I would have not written this bug
report while moving out the test case to falcon_team:
Bug #37831 falcon_bug_37080 fails with time out sometimes on Windows
Description:
falcon_bug_37080 fails with time out sometimes on Windows.
How to repeat:
See xref for failures. It failed on vm-win2003-32-a and win2003-x86.
falcon.falcon_bug_34890 [ pass ] 13141
falcon.falcon_bug_37080 [ fail ] timeout
Stopping All Servers
mysql-test-run: WARNING: Forcing kill of process 44500
Restoring snapshot of databases
Resuming Tests
>From the test description we see that it could be an internal deadlock:
#
# Bug#37080: Falcon deadlock on parallel TRUNCATE and INSERT
#
3) I won't delete a test case, even if it looks strange or useless :)
Cheers,
Hakan
--
Hakan Küçükyılmaz, Senior Software Engineer DBTG/MySQL +49 160
98953296
Sun Microsystems GmbH Sonnenallee 1, DE-85551 Kirchheim-Heimstetten
Geschaeftsfuehrer: Thomas Schroeder, Wolfang Engels, Dr. Roland Boemer
Vorsitz d. Aufs.rat.: Martin Haering HRB MUC 161028 49.011, 8.376
