A recent issue reproduction experience running a resmoke ESE test yielded a positive testing result, though there were BACKTRACE's reported in the logs during the shutdown phase. 

It would be useful to add a shutdown cleanness checking, as unclean shutdowns could sometimes cause serious consequences like data corruption, which should be captured and reflected on the testing result.

It may also worth considering how widespread this improvement should be applied, e.g. certain resmoke tests, all resmoke tests, other tests running on Evergreen.