Make maria.repair more resiliant for different failures

This is because on different compilation and server configurations the
memory usage is different and the query can get killed in different places
with different error messages as a result.

Reviewer: None (trival change)

mysql-test/suite/maria/repair.result

@@ -29,12 +29,5 @@ CREATE TABLE t1 (i INT) ENGINE=Aria;
 INSERT INTO t1 VALUES (1);
 SET max_session_mem_used=50000;
 REPAIR LOCAL TABLE t1 USE_FRM;
-Table	Op	Msg_type	Msg_text
-t1	repair	error	Failed to open partially repaired table
-Warnings:
-Error	1290	The MariaDB server is running with the --max-thread-mem-used=50000 option so it cannot execute this statement
 REPAIR LOCAL TABLE t1;
-Table	Op	Msg_type	Msg_text
-test.t1	repair	Error	The MariaDB server is running with the --max-thread-mem-used=50000 option so it cannot execute this statement
-test.t1	repair	error	Corrupt
 DROP TABLE t1;

mysql-test/suite/maria/repair.test

@@ -36,6 +36,8 @@ DROP TABLE t1;
 CREATE TABLE t1 (i INT) ENGINE=Aria;
 INSERT INTO t1 VALUES (1);
 SET max_session_mem_used=50000;
+--disable_result_log
 REPAIR LOCAL TABLE t1 USE_FRM;
 REPAIR LOCAL TABLE t1;
+--enable_result_log
 DROP TABLE t1;