InnoDB should refuse to start if crash recovery fails instead of asserting

2015-09-16 15:21:28 7fd806d4e780  InnoDB: Operating system error number 2 in a file operation.

InnoDB: The error means the system cannot find the path specified.

InnoDB: If you are installing InnoDB, remember that you must create

InnoDB: directories yourself, InnoDB does not create them.

InnoDB: Error: could not open single-table tablespace file ./test/#sql-5a51_9#P#p0.ibd

2015-09-16 15:21:28 140565804279680 [Note] InnoDB: Restoring possible half-written data pages 

2015-09-16 15:21:28 140565804279680 [Note] InnoDB: from the doublewrite buffer...

InnoDB: Set innodb_force_recovery to ignore this error.

2015-09-16 15:21:28 7fd806d4e780  InnoDB: Assertion failure in thread 140565804279680 in file log0recv.cc line 2776

InnoDB: We intentionally generate a memory trap.

InnoDB: Submit a detailed bug report to http://bugs.mysql.com.

InnoDB: If you get repeated assertion failures or crashes, even

InnoDB: immediately after the mysqld startup, there may be

InnoDB: corruption in the InnoDB tablespace. Please refer to

InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html

InnoDB: about forcing recovery.

150916 15:21:28 [ERROR] mysqld got signal 6 ;