Creating a new variant in the wiredtiger evergreen.yml doesn't work as the find_gperftools script isn't executed correctly during the "configure wiredtiger" function.

It calls it via: . automation-scripts/evergreen/find_gperftools.sh ${s3_access_key} ${s3_secret_key} ${build_variant} $is_cmake_build, passing the new build_variant defined by the new variant definition. The find_gperftools.sh script expects that it won't succeed if the variant is new and hasn't had artifacts dropped into S3 and thus the call to aws s3 ls returns non 0. However the calling function "configure wiredtiger" specifies set -o errexit so when the aws s3 ls fails the function exits and the gperf tools aren't built and dropped into s3.

The fix appears to be removing the set -o errexit from the "configure wiredtiger" function in the evergreen.yml file however this could have unintended side effects. I have an example patch build created.