Sometimes our qa tests will time out because an execution of one of the mongo tools has hung. While the current Evergreen config does clean up this executions, it could be improved. Once all the tools have been killed, resmoke usually exits and produces its report file. If the config uploaded the report file after it killed the processes, Evergreen may be able to show more relevant information on the build status pages. Additionally, we could use SIGABRT to kill the tools processes, which would print a full stack trace. This would be useful for debugging.