autotuner should catch compilation failures

[skimo-openhub]

By its very nature, the autotuner is not deterministic.
It may sometimes uncover compilation failures on the CI,
but these cause an abort instead of printing the feature vector
that could be used to reproduce the issue.
See, e.g., #181.

We probably need to redefine the CHECK macros to throw an exception,
at least when run under the autotuner.
Unfortunately, calling google::InstallFailureFunction to set a function that
throws an exception does not have the desired effect.
See also google/glog#249

[skimo-openhub]

Closed by #460.