This bug is triggered if ecc_fast._libsecp256k1 and/or
crypto.AES are not present.
Before, if the first test would have raised an exception
it would have been implicitly caught by returning from
the finally block and hence this effectively masks the
test's outcome. Now, the exception is properly propagated
causing the test to fail if an exception is raised.