Mongot publishes three binaries: 

https://mciuploads.s3.amazonaws.com/fts/atlas-search-localdev/mongot_latest_linux_aarch64.tgz
https://mciuploads.s3.amazonaws.com/fts/atlas-search-localdev/mongot_latest_linux_x86_64.tgz
https://mciuploads.s3.amazonaws.com/fts/atlas-search-localdev/mongot_latest_macos_x86_64.tgz

We should make patches to test which variants on server's evergreen projects (master, v7.0, v6.0, v5.0) support which of mongot's three binaries. It should be possible to do this by adding an evergreen task to each variant** that downloads a mongot binary (via curl) and places it in the install dir (eg build/install/dir), define a task for running the suite's test and adding that task to each evergreen variant as well.

• • I think it's possible to define a task a single time and have multiple variants call this task

• • alternatively, I believe there are git rules that know to ignore everything in the build/ folder – so it seems possible to remove those git ignore rules for the purposes of this ticket and push up patches that have a given binary included (For this to work, you will have had to download the binaries from the links above, scp them to your VM and untar the tar packages)