There have been a few cases recently where we somehow (on the mongodb-mongo-v3.2 project) end up running the 3.2 MongoDB binaries against tests from master. Until EVG-943 is implemented, all Evergreen projects are responsible for cleaning up directories they'll use themselves. We should add a check after extracting the artifacts and binaries that asserts the version string in compile_expansions.yml from the artifacts is identical to the version string from one of the MongoDB binaries (e.g. the mongo shell).

suffix: latest
src_suffix: latest
version: 3.3.3-217-gae3ee1c