SERVER-126317ClosedDone
Evergreen should mark FuzzTests as failed when they crash
FuzzTests are intended to run for a long period of time, and potentially surface multiple issues. As a result, the harness will observe crashes, record them to a special crash directory, and keep fuzzing. It seems to have a trick to keep itself from repeatedly hitting the same condition. After the target fuzz time elapses, the harness does not return a bad exit code to the shell. This causes resmoke to believe that the test "passed", and evergreen will mark the test as successful. An an examp