Fix test case for Bug #25347 so that it actually tests the code fix,

and so that it works correctly on Windows.


mysql-test/r/mysqlcheck.result:
  Flush tables before monkeying around with underlying MyISAM data files
mysql-test/t/mysqlcheck.test:
  Fix the test case for bug #25347 so that it actually does test the behavior.
  Also, this makes it work on Windows by ensuring that mysqld doesn't hold the
  underlying MyISAM files open while we try to corrupt them on disk.
  
  Flush tables before monkeying around with underlying MyISAM data files;
  --use-frm, so that mysqlcheck will succeed.

mysql-test/r/mysqlcheck.result

@@ -50,6 +50,7 @@ create database d_bug25347;
 use d_bug25347;
 create table t_bug25347 (a int);
 create view v_bug25347 as select * from t_bug25347;
+flush tables;
 removing and creating
 d_bug25347.t_bug25347                              OK
 drop view v_bug25347;

mysql-test/t/mysqlcheck.test

@@ -47,11 +47,12 @@ create database d_bug25347;
 use d_bug25347;
 create table t_bug25347 (a int);
 create view v_bug25347 as select * from t_bug25347;
+flush tables;
 --echo removing and creating
 --remove_file $MYSQLTEST_VARDIR/master-data/d_bug25347/t_bug25347.MYI
 --write_file $MYSQLTEST_VARDIR/master-data/d_bug25347/t_bug25347.MYI
 EOF
---exec $MYSQL_CHECK --repair --databases d_bug25347
+--exec $MYSQL_CHECK --repair --databases --use-frm d_bug25347
 drop view v_bug25347;
 drop table t_bug25347;
 drop database d_bug25347;