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.


Yes, I can either use the error_code version and ignore the result or try catch it?