If the generate.tasks of s3.put fail in the teardown commands of resmoke_tests, they dont cause the task to fail. The results tasks like //buildscripts/resmokeconfig:core will almost certainly fail, but it won't be obvious why.

We should try to make this more robust, and when they fail for reasons outside of our control, make it obvious why.

For example https://spruce.mongodb.com/version/6984fc33d1d4490007801d66/tasks?sorts=STATUS%3AASC%3BBASE_STATUS%3ADESC has a bunch of "SYSTEM FAILED" with the error: AccessDenied: User: arn:aws:iam::557821124784:user/srv-evg-mongodb-mongo-s3-key is not authorized to perform: s3:ListBucket on resource: "arn:aws:s3:::mciuploads" because no identity-based policy allows the s3:ListBucket action