innodb.innodb_bug14147491 sporadically fails in buildbot due to wrong error number

innodb.innodb_bug14147491 'innodb_plugin' w1 [ fail ]

        Test ended at 2017-04-27 17:07:58

CURRENT_TEST: innodb.innodb_bug14147491

mysqltest: At line 76: query 'SELECT * FROM t1' failed with wrong errno 1712: 'Index t1 is corrupted', instead of 1932...

The result from queries just before the failure was:

call mtr.add_suppression("InnoDB: Table \"test\".\"t1\" is corrupted. Please drop the table and recreate.");

call mtr.add_suppression("InnoDB: Cannot open table test/t1 from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.");

call mtr.add_suppression("InnoDB: Database page corruption on disk or a failed file read of tablespace test/t1 page  \[page id: space=[0-9]+, page number=[0-9]+\]. You may have to recover from a backup.");

# Create and populate the table to be corrupted

set global innodb_file_per_table=ON;

CREATE TABLE t1 (a INT AUTO_INCREMENT PRIMARY KEY, b TEXT) ENGINE=InnoDB;

INSERT INTO t1 (b) VALUES ('corrupt me');

INSERT INTO t1 (b) VALUES ('corrupt me');

# Backup the t1.ibd before corrupting

# Corrupt the table

Munged a string.

Munged a string.

# The below SELECT query will return that table is not

# in engine because table is corrupted

SELECT * FROM t1;

Warnings from just before the error:

Warning 180 InnoDB: Index "PRIMARY" for table "test"."t1" is marked as corrupted