Test innodb.innodb_mysql is unstable

[Laurynas Biveinis]

On 5.6 trunk:

innodb.innodb_mysql w3 [ fail ]
        Test ended at 2017-01-25 08:46:00

CURRENT_TEST: innodb.innodb_mysql
--- /mnt/workspace/percona-server-5.6-trunk/BUILD_TYPE/debug/Host/ubuntu-xenial-64bit/mysql-test/suite/innodb/r/innodb_mysql.result 2017-01-25 15:06:24.252887018 +0300
+++ /mnt/workspace/percona-server-5.6-trunk/BUILD_TYPE/debug/Host/ubuntu-xenial-64bit/build/mysql-test/var/3/log/innodb_mysql.reject 2017-01-25 16:46:00.100281421 +0300
@@ -389,7 +389,7 @@
 # Masking (#) number in "rows" column of the following EXPLAIN output, as it may vary (bug#47746).
 EXPLAIN SELECT DISTINCT t1.name, t1.dept FROM t1 WHERE t1.name='rs5';
 id select_type table type possible_keys key key_len ref rows Extra
-1 SIMPLE t1 range name name 44 NULL # Using where; Using index for group-by
+1 SIMPLE t1 ref name name 22 const # Using where; Using index
 SELECT DISTINCT t1.name, t1.dept FROM t1 WHERE t1.name='rs5';
 name dept
 DROP TABLE t1;

mysqltest: Result content mismatch

[Laurynas Biveinis (laurynas-biveinis)]

     https://github.com/percona/percona-server/pull/1363
     https://github.com/percona/percona-server/pull/1364

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3630