Comment 9 for bug 363181

patrick_crews <email address hidden> writes:

> No problems and my apologies for the incomplete .trace files. I gathered
> them via ./mysql-test-run.pl --force --repeat=2 mysql_client_test and didn't
> do anything beyond packaging them.

No need to apologise. In fact I am completely baffled as to how the trace
files could be incomplete in that way. I thought about disk full, but the
trace files contains traces from two runs (due to --repeat=2 I assume), and
they are identical, including how they are incomplete. It just doesn't make
sense...

> However, this seems to now be a moot point. After refreshing my Maria tree,
> the failure has gone away and I cannot repeat it any longer. I have tried
> multiple runs of the test itself as well as running the full suite without a
> failure.
>
> The changes I pulled were to:
> M libmysql/libmysql.c
> M tests/mysql_client_test.c

Right. I fixed some minor problems with the dbug, which were visible in the
trace file.

Hm. I guess it is remotely possible that this actually fixes the problem. I
somewhat doubt it though.

The problem is that this failure seems extremely fragile, I used to be able to
repeat it as well, but then it disappeared.

One thing you can try is to run the test in a tight loop:

    (for i in `seq 1 100`; do echo XXX $i XXX; ./mysql-test-run.pl mysql_client_test || exit 1; done)

This will run the test up to 100 times until it fails. If you cannot repeat
it this way, we will have to declare the problem fixed by the above changes
until someone else manage to repeat it.

Thanks for the effort,

 - Kristian.