Don't swallow log messages that are null but have a throwable

In some places, I log using:

    Timber.e(throwable, throwable.getMessage())

If the throwable in question was created with a null or empty message, the log message would disappear into the ether. This pull request causes the stack trace to be logged with an empty message instead.
I don't think you need to use a thread in these tests.