These two Evergreen tasks for the different build variants have the same binaries url:

• https://spruce.mongodb.com/task/mongodb_mongo_master_nightly_enterprise_rhel_83_s390x_archive_dist_test_eced867739c05384f20dbebdcde50916d9ab8420_23_09_23_23_51_49/files?execution=0
• https://spruce.mongodb.com/task/mongodb_mongo_master_nightly_enterprise_rhel_83_s390x_dynamic_archive_dist_test_eced867739c05384f20dbebdcde50916d9ab8420_23_09_23_23_51_49/files?execution=0

Notably, the binaries url is the result of compiling with --link-model=dynamic despite the "Enterprise RHEL 8.3 s390x" build variant using --link-model=static.

The problem is due to the two build variants sharing the same value for the compile_variant expansion. This causes the two build variants to write to the same S3 path and whichever build variant happens to run its archive_dist_test Evergreen task second in wall-clock time wins. The compile_variant expansion must instead be overridden for the "Enterprise RHEL 8.3 s390x Shared" build variant.

Note that the same issue applies to the "Enterprise RHEL 8.1 PPC64LE Shared" and "Enterprise RHEL 8.1 PPC64LE" build variants.