Fixes segfault caused by accessing destroyed logging object when test fi...

The order of destruction of static objects after the tests finish is the reverse of the order of construction, so logging first then the environment. A logic error in the code, during the destruction of the environment, was checking whether the bootstrap file is successfully removed and if it is attempts to log the error.


Cool Brian, perhaps the error_code route and maybe even an assert ? I think the problem would be if the dir was there and we could not delete it, if its already gone for some reason then its OK. So perhaps an exists check then delete ? although (you will know better than me here) it may be this dir is guaranteed to be there on destruction.