David Wells

Ah - splitting the tests is fine, but when I ran this on my machine I didn't see any of the `check` tests run (it sounds like you noticed the...

Yeah, I think we need to explicitly list the tests - it's tedious but better than globbing inside the build system. This still has the problem with load balancing tests...

`TBOX_ERROR` comes from SAMRAI - it resolves down to calling `MPI_Abort()`, `abort()`, or `exit()`.

What's the issue with that case? If we abort then we have a nonzero exit code anyway.

The one test that utilizes this is `subdomain_level_translation_01.expect_error=true.input` - we could probably rig it up to exit(-1) instead.

No - I don't think there is a way to toggle back to exit.

Oh yeah, I remember that one: https://github.com/IBAMR/IBAMR/blob/master/tests/IBFE/interpolate_velocity_02.cpp We can probably delete that test :) Just ignore it for now.

I don't know what's going on with that child integrator test. I'll take a look at your new version.

Yes, but it doesn't make any sense that the executable would abort when run under `ctest` and not under `attest`.

An example of this is handling IB data in #492: it would be better to handle all of this in a common base class.