SERVER-91111 and SERVER-81396 are issues where the compile_variant Evergreen expansion was misused and got inherited by another build variant which does its own compilation and ends up non-deterministically overwriting the MongoDB binaries depending on when the two compiling build variants are run. This mistake may or may not lead to test failures depending on the compile_flags supplied but erodes trust in the testing infrastructure doing what we believed it to be doing.

Adding a custom lint step for the Evergreen project configuration to ensure all build variants with the same mongo_binaries Evergreen expansion (which itself derives from these other Evergreen expansions) have exactly one build variant among the set with an archive_dist_test Evergreen task would prevent this type of mistake.

There may be other artifacts which are also prone to being overwritten by different build variants due to the usage of YAML anchors and aliases. The MongoDB binaries are particularly sensitive and can be worth starting there. SERVER-72601 was an example where the resmoke-constants.tgz file was overwritten by the "future git tag" build variant.