unit-test-with-compile function is not required in evergeen.yml as there already exists unit-test function that performs the same steps, the only difference is that in unit-test-with-compile function, compilation is embedded within the task whereas in unit-test function, the WiredTiger binaries are fetched.

unit-test-with-compile function was introduced in the evergreen.yml, due to WT-7293. As described in the ticket the error occurred due to the compile and unit-test tasks running on different hosts with different toolchain versions, with the former on macos-1012 and latter on macos-1014. The unit-test task tries to download the artifacts generated by the compile task and hit the issue as the library path is different on the 2 building hosts. 

Since, we do not run compilation task on macos-1012, we can compile on a different host.