Trilinos: testing using floating point exceptions

Created by: jjellio

I've worked through an issue where Trilinos' test suite passed all tests, yet an app observed failures. The general method for handling a situation like this is to isolate the error, determine a fix, create a unit test that manifests the error, then push the fix and unit test. The more interesting point is how the app runs its unit tests.

A version of the app's nightly test suite runs certain (perhaps all) unit tests with floating point exceptions enabled. It seems like Trilinos should do the same, or atleast consider the cost/benefit of doing so.

@trilinos/framework